Re: Dependency graph for Emacs Lisp files

[Lars Ingebrigtsen <larsi@gnus.org>]

phillip.lord@russet.org.uk (Phillip Lord) writes:

> `make check` currently uses the a fudge based on name matching between
> tests and source files, but it missed any other form of
> dependency. Having something better would be nice. I think autoloads
> dependencies might be more thatn 3% of the problem, though, but if you
> add a mechanism based on `require` then an autoload dependency could be
> added later.

autoloads generally don't lead to compilation breakages, do they?  You
can't autoload a macro meaningfully, or a variable...

> Rather than creating "dependency.el", though, why not create an
> includeable Makefile? That way you might need to delete anything, just
> let Make to it's dependency thing.

I am no make expert at all, so I don't quite know what that would look
like.

My thought was that if file A.el depended on file B.el, and B.el has
changed, then there would just be a step in the compilation process that
deleted both A.elc and B.elc, and then the rest of the process would
continue on as before.

(We need to delete B.elc because otherwise `(require B)' in A.el would
load the old B.elc, and A.el might be byte-compiled before B.el.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no