This is the mail archive of the automake@gnu.org mailing list for the automake project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: auto-regenerating Makefile.in and Makefile files


Tom Tromey <tromey@redhat.com> writes:

|> >>>>> "Earnie" == Earnie Boyd <earnie_boyd@yahoo.com> writes:
|> 
|> Earnie> Wouldn't this work anyway because you had to change the
|> Earnie> top-level Makefile.am or configure.in to include the new
|> Earnie> SUBDIR?  I.E.: Makefile.in : Makefile.am configure.in
|> 
|> The problem is that the Makefile always runs config.status to recreate
|> just a single Makefile (the current one).  The question is: what
|> Makefile decides to generate the new Makefile for the first time?
|> Or, for that matter, the new Makefile.in?

There is none.  You need to re-run configure when a new makefile is added
(you can use ./config.status --recheck && ./config.status for that).

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]