alex wrote: > Why is it needed though? If new files have been added to the build I'd > expect failures at the link stage rather than mysterious broken binaries > getting generated.
I don't think it happens only when adding new files e.g., it definitely happens as well when adding/removing properties. For example, if you add a #include directive, the generated Makefiles in your object directory do not reflect this dependencies as they were generated before updating the sources. > We have some rules in the makefiles to re-run the dependency generation. > Is there some magic we could add to the Makefiles to clean and > re-generate everything from scratch when CVS has changed "enough"? Add a dependency on ChangeLog and blame the bad guy who's too lazy to document his changes? If you remember to run "make depend" after each CVS update, there should be no problem. -- Christian
pgpKQ1NkZdAV5.pgp
Description: PGP signature
