>That would be fine, if that even worked, that would probalby solve about 90% of the problems just by cleverly odering the includes... but, as I started, the first attached makefile fails, and it includes 'ticks' which if Makefile or one of the other touchable things changes, remakes ticks, which should cause a reload with the current, updated value. Then x is included, and again, x needs to be updated, which will cause x to be regenerated with the current value of ticks, which in turn should do the same for y....
I think this only happens at the time the makefile is included. It's infeasible to have make check whether all makefiles that it had included, has been touched by something.
but this is not what happens, and what you're really saying is that only the LAST included file can be re-loaded, since ALL includes are read before their dependancies are even checked.
And THAT is not at all what the documentation indicates, it says -
" if any have actually been changed, make starts with a clean slate and reads all the makefiles over agai"
if ANY changed, clean all, and reload all again...
Noel
_______________________________________________ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-make
