pkgsrc/devel/ncurses/buildlink3.mk

# $NetBSD: buildlink3.mk,v 1.24 2004/10/03 00:13:31 tv Exp $

BUILDLINK_DEPTH:=	${BUILDLINK_DEPTH}+
NCURSES_BUILDLINK3_MK:=	${NCURSES_BUILDLINK3_MK}+

.if !empty(BUILDLINK_DEPTH:M+)
BUILDLINK_DEPENDS+=	ncurses
.endif

BUILDLINK_PACKAGES:=	${BUILDLINK_PACKAGES:Nncurses}
BUILDLINK_PACKAGES+=	ncurses

.if !empty(NCURSES_BUILDLINK3_MK:M+)
BUILDLINK_DEPENDS.ncurses+=	ncurses>=5.3nb1
BUILDLINK_RECOMMENDED.ncurses+=	ncurses>=5.4nb1
BUILDLINK_PKGSRCDIR.ncurses?=	../../devel/ncurses
.endif	# NCURSES_BUILDLINK3_MK

BUILDLINK_DEPTH:=	${BUILDLINK_DEPTH:S/+$//}
Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10 in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include. 2004-10-03 02:12:51 +02:00			`# $NetBSD: buildlink3.mk,v 1.24 2004/10/03 00:13:31 tv 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}+`
			`NCURSES_BUILDLINK3_MK:= ${NCURSES_BUILDLINK3_MK}+`

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			`.if !empty(BUILDLINK_DEPTH:M+)`
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. 2004-01-04 00:06:43 +01:00			`BUILDLINK_DEPENDS+= ncurses`
			`.endif`

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_PACKAGES:= ${BUILDLINK_PACKAGES:Nncurses}`
			`BUILDLINK_PACKAGES+= ncurses`
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. 2004-01-04 00:06:43 +01:00
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			`.if !empty(NCURSES_BUILDLINK3_MK:M+)`
			`BUILDLINK_DEPENDS.ncurses+= ncurses>=5.3nb1`
Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10 in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include. 2004-10-03 02:12:51 +02:00			`BUILDLINK_RECOMMENDED.ncurses+= ncurses>=5.4nb1`
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_PKGSRCDIR.ncurses?= ../../devel/ncurses`
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. 2004-01-04 00:06:43 +01:00			`.endif # NCURSES_BUILDLINK3_MK`

Use S/+$// instead of C/\+$// to save a backslash. Very highly recommended by seb :) 2004-01-05 12:05:44 +01:00			`BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH:S/+$//}`