dependencies

Subject: dependencies
From: Aaron Lehmann (aaronl@vitelus.com)
Date: Fri Jun 16 2000 - 17:15:48 CDT

• sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Next message: Bernhard Rosenkraenzer: "Patch: fix compilation on IA64"
• Previous message: WJCarpenter: "Re: smart quotes, et al"

Looking at gcc's man page, gcc can automatically make dependency rules for
files. For example:

$ gcc -M ut_vector.cpp -I../unix/
ut_vector.o: ut_vector.cpp /usr/include/stdlib.h \
 /usr/include/features.h /usr/include/sys/cdefs.h \
 /usr/include/gnu/stubs.h \
 /usr/lib/gcc-lib/i386-linux/2.95.2/include/stddef.h \
 /usr/include/sys/types.h /usr/include/bits/types.h \
 /usr/include/time.h /usr/include/endian.h /usr/include/bits/endian.h \
 /usr/include/sys/select.h /usr/include/bits/select.h \
 /usr/include/bits/sigset.h /usr/include/sys/sysmacros.h \
 /usr/include/alloca.h ut_types.h ut_vector.h ut_assert.h \
 /usr/include/assert.h ../unix/ut_unixAssert.h

An optional 'make dep' stage in the build process that would update the
dependency information and make sure that when rebuilding, only necessary
files are rebuilt would increase my productivity a lot. For people
compiling the source, it would still be without dependency rules like it
is now, but if a developer ran 'make dep' it would update the makefiles so
that they have valid dependency information for recompiling. What do you
guys think about having some simple dependency management?

Aaron Lehmann

• Next message: Bernhard Rosenkraenzer: "Patch: fix compilation on IA64"
• Previous message: WJCarpenter: "Re: smart quotes, et al"

This archive was generated by hypermail 2b25 : Fri Jun 16 2000 - 17:15:51 CDT