kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/lang/gcc3-c++/buildlink3.mk

37 lines
1 KiB
Makefile
Raw Normal View History

If the ${PKGBASE} of a package doesn't match the token passed to BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
2004-03-16 19:23:26 +01:00
# $NetBSD: buildlink3.mk,v 1.7 2004/03/16 18:23:27 jlam Exp $
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH}+
GCC3CXX_BUILDLINK3_MK:= ${GCC3CXX_BUILDLINK3_MK}+
.include "../../mk/bsd.prefs.mk"
bsd.compiler.mk no longer adds dependencies or includes buildlink*.mk files if it's being included by bsd.prefs.mk, so we can safely move the BUILDLINK_DEPENDS line to its usual location.
2004-02-05 04:45:13 +01:00
.if !empty(BUILDLINK_DEPTH:M+)
BUILDLINK_DEPENDS+= gcc3cxx
.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:Ngcc3cxx}
BUILDLINK_PACKAGES+= gcc3cxx
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
.if !empty(GCC3CXX_BUILDLINK3_MK:M+)
Check if a variable is defined before checking its value.
2004-02-13 01:27:28 +01:00
. if defined(GCC3_INSTALLTO_SUBPREFIX)
. if ${GCC3_INSTALLTO_SUBPREFIX} != "gcc3"
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
GCC3_PKGMODIF= _${GCC3_INSTALLTO_SUBPREFIX}
Check if a variable is defined before checking its value.
2004-02-13 01:27:28 +01:00
. endif
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
. endif
If the ${PKGBASE} of a package doesn't match the token passed to BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
2004-03-16 19:23:26 +01:00
BUILDLINK_PKGBASE.gcc3cxx?= gcc3${GCC3_PKGMODIF}-c++
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
BUILDLINK_DEPENDS.gcc3cxx+= gcc3${GCC3_PKGMODIF}-c++>=${_GCC_REQD}
BUILDLINK_PKGSRCDIR.gcc3cxx?= ../../lang/gcc3-c++
List the correct directories for finding GCC libraries so that they will be added automatically to library and run-time library search paths.
2004-02-05 01:28:35 +01:00
BUILDLINK_LIBDIRS.gcc3cxx?= \
lib ${_GCC_ARCHDIR:S/^${BUILDLINK_PREFIX.gcc3cxx}\///}
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
# Packages that link against shared libraries need a full dependency.
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
.if defined(USE_GCC_SHLIB)
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
BUILDLINK_DEPMETHOD.gcc3cxx+= full
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
.else
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
BUILDLINK_DEPMETHOD.gcc3cxx?= build
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
.endif
bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for use by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency is always added regardless of the BUILDLINK_DEPTH. This is because these buildlink3.mk files may be included by bsd.prefs.mk, which is often included other buildlink3.mk files, and we need to ensure that regardless of the depth, we are using the correct compiler.
2004-02-01 15:05:46 +01:00
.endif # GCC3CXX_BUILDLINK3_MK
BUILDLINK_DEPTH:= ${BUILDLINK_DEPTH:S/+$//}
Reference in a new issue Copy permalink