Re: Build-time dependencies

[David Kastrup]

Eli Zaretskii <address@hidden> writes:

>> From: Glenn Morris <address@hidden>
>> Cc: Alan Mackenzie <address@hidden>,  Eli Zaretskii <address@hidden>,  
>> address@hidden
>> Date: Sun, 08 Jun 2008 15:03:07 -0400
>> 
>> Stefan Monnier wrote:
>> 
>> > I think it should be easy to generate the dependencies from bytecomp.el
>> > (just record macros as we expand them, and then try and figure out
>> > which file they come from).  This way they could be kept uptodate
>> > 100% automatically.
>> 
>> What exactly is the point of doing this supposed to be?
>> To make non-bootstrap builds more reliable?
>
> To make dependencies between Lips files explicit in lisp/Makefile.in,
> and thus causing Make to compile Lisp files in the right order.  Right
> now, whenever some Lisp files change, I frequently need to "make
> recompile" several times, sometimes removing stale *.elc files
> manually, until it finally succeeds, because it basically compiles
> them in a random order.

Personally, I would appreciate it if we could get of the bootstrap
target altogether, and when Emacs chose to do a bootstrap on "make"
whenever things could require it.

Similar with the "clean" target.  Having special targets that will _not_
bootstrap even when it _could_ be necessary in order to make debugging
faster/easier is nice.

But I think without extra measures, it would be nice if "make" did
everything that might be required.  The combination of "recompile" and
"cvs-update" and "bootstrap" and "whatever-clean" in what ever
directories that one has to try whenever something looks like not
working:

That is not really the idea behind using make.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum