a93ea220fc
* DPSRCS contains extra dependencies, but is _NOT_ added to CLEANFILES. This is a change of behaviour. If a Makefile wants the clean semantics it must specifically append to CLEANFILES. Resolves PR toolchain/5204. * To recap: .d (depend) files are generated for all files in SRCS and DPSRCS that have a suffix of: .c .m .s .S .C .cc .cpp .cxx * If YHEADER is set, automatically add the .y->.h to DPSRCS & CLEANFILES * Ensure that ${OBJS} ${POBJS} ${LOBJS} ${SOBJS} *.d depend upon ${DPSRCS} * Deprecate the (short lived) DEPENDSRCS Update the various Makefiles to these new semantics; generally either adding to CLEANFILES (because DPSRCS doesn't do that anymore), or replacing specific .o dependencies with DPSRCS entries. Tested with "make -j 8 distribution" and "make distribution". |
||
---|---|---|
.. | ||
dist | ||
lib | ||
libexec | ||
usr.bin | ||
usr.sbin | ||
Makefile | ||
README |
$NetBSD: README,v 1.4 2002/09/22 09:47:56 wiz Exp $ Organization of Sources: This directory hierarchy is using a new organization that separates the GNU sources from the BSD-style infrastructure used to build the GNU sources. The GNU sources are kept in the standard GNU source tree layout under: dist/* The build infrastructure uses the normal BSD way under: lib/* usr.bin/* The makefiles in the above hierarchy will "reach over" into the GNU sources (src/gnu/dist) for everything they need. Maintenance Strategy: The sources under src/gnu/dist are generally a combination of some published distribution plus changes that we submit to the maintainers and that are not yet published by them. There are a few files that are never expected to be submitted to the FSF, (i.e. BSD-style makefiles and such) and those generally should stay in src/gnu/lib or src/gnu/usr.bin (the BSD build areas). Make sure all changes made to the GNU sources are submitted to the appropriate maintainer, but only after coordinating with the NetBSD maintainers by sending your proposed submission to the <tech-toolchain@netbsd.org> mailing list. Only send the changes to the third-party maintainers after consensus has been reached.