On Fri, 11 Jun 2010 18:55:59 +0200 Michael Stahl <[email protected]> wrote:
> > We did attempt to create non-recursive makefiles for CMake, and > > they are "less" recursive than they once were. However, we found > > it impossible to handle implicit dependencies of generated source > > files without using recursive calls to make. If you have a > > solution for that, we would be very receptive. > > i believe the gbuild system is designed so that GNU make will restart > itself automatically in such circumstances. > but i don't know how that works, maybe Björn will explain it... Hi all, see http://www.gnu.org/software/automake/manual/make/Remaking-Makefiles.html#Remaking-Makefiles for details: "To this end, after reading in all makefiles, make will consider each as a goal target and attempt to update it. If a makefile has a rule which says how to update it (found either in that very makefile or in another one) or if an implicit rule applies to it (see Using Implicit Rules), it will be updated if necessary. After all makefiles have been checked, if any have actually been changed, make starts with a clean slate and reads all the makefiles over again. (It will also attempt to update each of them over again, but normally this will not change them again, since they are already up to date.)" So this is done by including an not yet existing file and providing a rule for it -- GNU make will take care of the rest. Best Regards, Bjoern --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
