pkgsrc/devel/binutils/buildlink3.mk

# $NetBSD: buildlink3.mk,v 1.22 2008/03/24 23:40:37 tnn Exp $

BUILDLINK_DEPTH:=		${BUILDLINK_DEPTH}+
BINUTILS_BUILDLINK3_MK:=	${BINUTILS_BUILDLINK3_MK}+

.if ${BUILDLINK_DEPTH} == "+"
BUILDLINK_DEPENDS+=	binutils
.endif

BUILDLINK_PACKAGES:=	${BUILDLINK_PACKAGES:Nbinutils}
BUILDLINK_PACKAGES+=	binutils
BUILDLINK_ORDER:=	${BUILDLINK_ORDER} ${BUILDLINK_DEPTH}binutils

.if ${BINUTILS_BUILDLINK3_MK} == "+"
BUILDLINK_API_DEPENDS.binutils+=	binutils>=2.17
BUILDLINK_PKGSRCDIR.binutils?=	../../devel/binutils
BUILDLINK_DEPMETHOD.binutils?=	build
.endif	# BINUTILS_BUILDLINK3_MK

BUILDLINK_DEPTH:=		${BUILDLINK_DEPTH:S/+$//}
- Split out the code for overriding as(1) into it's own file. - In override-as.mk, fabricate a "specs" file and use it to force gcc into execvp'ing the correct as(1). Apparently having it in $PATH is not enough. This only affects multimedia/mplayer and perhaps sysutils/memtest86. (The latter probably doesn't need binutils at all, at least on modern NetBSD, and should be revisited.) 2008-03-25 00:40:37 +01:00			`# $NetBSD: buildlink3.mk,v 1.22 2008/03/24 23:40:37 tnn Exp $`
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. 2004-01-04 00:06:43 +01:00
			`BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH}+`
			`BINUTILS_BUILDLINK3_MK:= ${BINUTILS_BUILDLINK3_MK}+`

Regenerated 2007-05-29 14:27:24 +02:00			`.if ${BUILDLINK_DEPTH} == "+"`
Split out the code that deals with checking whether the software is built-in or not into a separate builtin.mk file. The code to deal checking for built-in software is much simpler to deal with in pkgsrc. The buildlink3.mk file for a package will be of the usual format regardless of the package, which makes it simpler for packagers to update a package. The builtin.mk file for a package must define a single yes/no variable USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether to use the built-in software or to use the pkgsrc software. 2004-03-10 18:57:14 +01:00			`BUILDLINK_DEPENDS+= binutils`
			`.endif`

			`BUILDLINK_PACKAGES:= ${BUILDLINK_PACKAGES:Nbinutils}`
			`BUILDLINK_PACKAGES+= binutils`
Change the format of BUILDLINK_ORDER to contain depth information as well, and add a new helper target and script, "show-buildlink3", that outputs a listing of the buildlink3.mk files included as well as the depth at which they are included. For example, "make show-buildlink3" in fonts/Xft2 displays: zlib fontconfig iconv zlib freetype2 expat freetype2 Xrender renderproto 2006-07-09 01:10:35 +02:00			`BUILDLINK_ORDER:= ${BUILDLINK_ORDER} ${BUILDLINK_DEPTH}binutils`
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. 2004-01-04 00:06:43 +01:00
Regenerated 2007-05-29 14:27:24 +02:00			`.if ${BINUTILS_BUILDLINK3_MK} == "+"`
			`BUILDLINK_API_DEPENDS.binutils+= binutils>=2.17`
			`BUILDLINK_PKGSRCDIR.binutils?= ../../devel/binutils`
			`BUILDLINK_DEPMETHOD.binutils?= build`
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. 2004-01-04 00:06:43 +01:00			`.endif # BINUTILS_BUILDLINK3_MK`

Aligned the last line of the buildlink3.mk files with the first line, so that they look nicer. 2006-04-12 12:26:59 +02:00			`BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH:S/+$//}`