pkgsrc/devel/libmm/buildlink3.mk

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

BUILDLINK_DEPTH:=	${BUILDLINK_DEPTH}+
LIBMM_BUILDLINK3_MK:=	${LIBMM_BUILDLINK3_MK}+

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

BUILDLINK_PACKAGES:=	${BUILDLINK_PACKAGES:Nlibmm}
BUILDLINK_PACKAGES+=	libmm

.if !empty(LIBMM_BUILDLINK3_MK:M+)
BUILDLINK_DEPENDS.libmm+=	libmm>=1.2.1
BUILDLINK_RECOMMENDED.libmm+=	libmm>=1.2.2nb1
BUILDLINK_PKGSRCDIR.libmm?=	../../devel/libmm
.endif	# LIBMM_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.6 2004/10/03 00:13:30 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}+`
			`LIBMM_BUILDLINK3_MK:= ${LIBMM_BUILDLINK3_MK}+`

Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk. 2004-01-05 00:34:04 +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+= libmm`
			`.endif`

Reorder location and setting of BUILDLINK_PACKAGES to match template buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk. 2004-03-05 20:25:06 +01:00			`BUILDLINK_PACKAGES:= ${BUILDLINK_PACKAGES:Nlibmm}`
			`BUILDLINK_PACKAGES+= libmm`

Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk. 2004-01-05 00:34:04 +01:00			`.if !empty(LIBMM_BUILDLINK3_MK:M+)`
Append to BUILDLINK_DEPENDS.<pkg> instead of setting a default value. In the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives a value only once due to the multiple inclusion protection in the bulldlink3.mk files. In the case where a package includes several buildlink3.mk files that each want a slightly different version of another dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the strictest <pkg> dependency to be matched. 2004-01-24 04:26:45 +01:00			`BUILDLINK_DEPENDS.libmm+= libmm>=1.2.1`
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.libmm+= libmm>=1.2.2nb1`
Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk. 2004-01-05 00:34:04 +01:00			`BUILDLINK_PKGSRCDIR.libmm?= ../../devel/libmm`
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework. 2004-01-04 00:06:43 +01:00			`.endif # LIBMM_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/+$//}`