On Thu, 2002-12-19 at 19:16, Jan Vroonhof wrote:
> > Ville> Seems that pdepends.mk still isn't
> > created by running a
> > Ville> "make autoloads" in a package dir,
> > Ville> ie. packages/xemacs-packages/<package>.
Is that necessary?
At the moment the pdepends.mk express the interdepencies between
the different packages, so they only make sense from the directory
one level above (i.e. from the Makefile in xemacs-packages).
Why? I don't see why compiling from different directories would have
any effect on the fact that some packages depend on others.
I agree this all very hacky, but it took quite a bit of effort to
right. This way Make can figure out all the proper dependencies with
out relying on the fact that you called the toplevel make autoload before
make bytecompile etc...
Exactly. And this is what I'd like to happen when building from a
package directory. It works the way it should from the packages/ or
(xemacs|mule)-packages/ level, but *not* from
packages/xemacs-packages/foo/, because pdepends.mk is not created or
$(BYTECOMPILE_TARGETS): %bytecompile.target: %autoloads.target
I see that this line has recently been commented out.. Why? Was there
I don't know, maybe it's accidental. Ben?
VANILLA = -vanilla -no-autoloads
so that any existing autoloads from already installed packages don't
get used by accident. I think -no-autoloads should be the default.
-no-autoloads is hardcoded in XEmacs.rules (BOOT_XEMACS), that shouldn't
be a problem.
Merry christmas to you all,
You too <:)
scop at xemacs.org