Follow-up Comment #4, bug #3116 (project make):
Just a guess what he meant:
If after changing a soiurce file a 'make clean' is done, it would be a good
thing to try to build the target first which has the newest date (the changed
one), as it is the one most likely to have errors.
This saves a lot of time sice emake stops after the first error (unless -k)
The bigger the project is, the longer it might take until the newly changed
file is compiled and make stops.
If the dependencies are set up properly, it is normally not necessary to call
a make clean. But in some projects it is necessary to 'hide' some dependencies
because e.g. an include file is constantly changed but these changes do not
affect most of the files which include it. E.g. a file with global
definitions whose current changes are only important for the C file currently
being worked on.
But, well, then one can recompile until there are no more errors and then
make a complete build.
Anyway, building the target with the newest prerequisite first would be a
nice idea.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=3116>
_______________________________________________
Nachricht geschickt von/durch Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
