On Dec 4, 2007, at 3:22 AM, IOhannes m zmoelnig wrote:
Russell Bryant wrote:
I'm not positive, but I don't think that this is going to do exactly what you're looking for.
All that the makefile.dependencies target is going to do now is automatically generate it if it doesn't exist. However, you want it generated any time that the dependencies may have changed, which is when any of the source changes.
On a related note, since this file is automatically generated, and is system specific, why is checked in to CVS?
Another question, why does the clean target create an empty makefile.dependencies file after deleting any existing one? That doesn't seem right to me ...
i guess the answer to all of your questions is: makefile.dependencies has to my knowledge not been used for years! it just get's created (or not), but it is never included into build-process, so it would be better to just remove it.
It's included at the bottom of makefile.in and makefile.mingw like this:
include makefile.dependencies
I don't about order of includes in makefiles, but it is being included.
.hc
Anyway, back to the original point of the message, I would suggest the following change:
btw, the gnu make manual suggest to use one dependency makefile per sourcefile, instead of one general makefile.depend.
something like:
<snip>
-include $(SOURCES:.c=.d) endif
%.d: %.c @set -e; rm -f $@; \ $(CC) $(MAKEDEP_FLAGS) $(CFLAGS) $< > $@.$$$$; \ sed 's,($*).o[ :]*,\1.o $@ : ,g' < $@.$$$$ > $@; \ rm -f $@.$$$$
</snip>
(this example is copied from the Gem sources, so it might not work out of the box for pd, but you should get the idea)
more information can be found here: http://www.gnu.org/software/make/manual/make.html#Automatic- Prerequisites
mfgas.d IOhannes
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------ ----