freebsd-skq/tools/build/mk/Makefile.boot

# $FreeBSD$

# FreeBSD didn't always have the __FBSDID() macro in <sys/cdefs.h>.
# We could do this with a sys/cdefs.h wrapper, but given that this would
# slow down all new builds for such a simple concept, we do it here.
.if ( ${BOOTSTRAPPING} < 440001 || \
    ( ${BOOTSTRAPPING} >= 500000 && ${BOOTSTRAPPING} < 500024 ))
CFLAGS+=	-D__FBSDID=__RCSID
.endif

CFLAGS+=	-I${WORLDTMP}/legacy/usr/include
DPADD+=		${WORLDTMP}/legacy/usr/lib/libegacy.a
LDADD+=		-legacy
LDFLAGS+=	-L${WORLDTMP}/legacy/usr/lib
Migrate to a new way of dealing with building from old revisions of FreeBSD. This method attempts to centralize all the necessary hacks or work arounds in one of two places in the tree (src/Makefile.inc1 and src/tools/build). We build a small compatibility library (libbuild.a) as well as selectively installing necessary include files. We then include this directory when building host binaries. This removes all the past release compatibilty hacks from various places in the tree. We still build on tip of stable and current. I will work with those that want to support more, although I anticipate it will just work. Many thanks to ru@, obrien@ and jhb@ for providing valuable input at various stage of implementation, as well as for working together to positively effect a change for the better. 2003-04-05 20:30:30 +00:00			`# $FreeBSD$`

			`# FreeBSD didn't always have the __FBSDID() macro in <sys/cdefs.h>.`
We can't use ${WORLDTMP}/usr/{include,lib} for the compat layer. This is because we populate these directories later, and a subsequent -DNOCLEAN build may fail. So, we put them in ${WORLDTMP}/build/usr/{include,lib} instead and adjust Makefile.boot. Again, this works on -stable and -current, but might break older versions. Submitted by: ru@ 2003-04-06 03:50:28 +00:00			`# We could do this with a sys/cdefs.h wrapper, but given that this would`
			`# slow down all new builds for such a simple concept, we do it here.`
Make sure legacy stuff comes last. Some tools that use legacy stuff (binutils) depend on this order. For this to work, provide (and use) specialized versions of bsd.prog.mk and bsd.lib.mk that include the standard versions first, then augment CFLAGS, DPADD, LDADD, and LDFLAGS as necessary, with the legacy stuff. Tested on: 4.0-RELEASE 2003-04-12 15:07:46 +00:00			`.if ( ${BOOTSTRAPPING} < 440001 \|\| \`
Migrate to a new way of dealing with building from old revisions of FreeBSD. This method attempts to centralize all the necessary hacks or work arounds in one of two places in the tree (src/Makefile.inc1 and src/tools/build). We build a small compatibility library (libbuild.a) as well as selectively installing necessary include files. We then include this directory when building host binaries. This removes all the past release compatibilty hacks from various places in the tree. We still build on tip of stable and current. I will work with those that want to support more, although I anticipate it will just work. Many thanks to ru@, obrien@ and jhb@ for providing valuable input at various stage of implementation, as well as for working together to positively effect a change for the better. 2003-04-05 20:30:30 +00:00			`( ${BOOTSTRAPPING} >= 500000 && ${BOOTSTRAPPING} < 500024 ))`
			`CFLAGS+= -D__FBSDID=__RCSID`
			`.endif`

-legacy and /.../legacy/... looks better than build or bootstrap in the logs, so use that instead. Submitted by: obrien. 2003-04-06 21:46:44 +00:00			`CFLAGS+= -I${WORLDTMP}/legacy/usr/include`
Make sure legacy stuff comes last. Some tools that use legacy stuff (binutils) depend on this order. For this to work, provide (and use) specialized versions of bsd.prog.mk and bsd.lib.mk that include the standard versions first, then augment CFLAGS, DPADD, LDADD, and LDFLAGS as necessary, with the legacy stuff. Tested on: 4.0-RELEASE 2003-04-12 15:07:46 +00:00			`DPADD+= ${WORLDTMP}/legacy/usr/lib/libegacy.a`
			`LDADD+= -legacy`
			`LDFLAGS+= -L${WORLDTMP}/legacy/usr/lib`