kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/db3/buildlink3.mk

32 lines
834 B
Makefile
Raw Normal View History

Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
# $NetBSD: buildlink3.mk,v 1.16 2004/11/15 17:54:49 jlam 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}+
DB3_BUILDLINK3_MK:= ${DB3_BUILDLINK3_MK}+
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
.include "../../mk/bsd.prefs.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+= db3
.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:Ndb3}
BUILDLINK_PACKAGES+= db3
Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.
2004-01-05 00:34:04 +01:00
.if !empty(DB3_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.db3+= db3>=2.9.2
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.db3+= db3>=3.11.2nb3
Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.
2004-01-05 00:34:04 +01:00
BUILDLINK_PKGSRCDIR.db3?= ../../databases/db3
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
BUILDLINK_INCDIRS.db3?= include/db3
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
BUILDLINK_LDADD.db3= -ldb3
Transform -ldb-[34] to -ldb[34], respectively, as they're the better known names for the newer Sleepycat DB libraries.
2004-03-22 19:18:26 +01:00
BUILDLINK_TRANSFORM+= l:db-3:db3
Rework the Berkeley DB detection in buildlink3: * Add a db1.builtin.mk file that detects whether DB-1.85 functionality exists in the base system, and remove the distinction between "native" and the other Berkeley DB packages -- we now refer to db[1234]. This paves the way for any future databases/db1 package. * USE_DB185 shouldn't need to be set by any packages -- its correct value is now automatically determined by bdb.buildlink3.mk depending on whether we explicitly request db1 or not. By default, if you include bdb.buildlink3.mk, you want DB-1.85 functionality and USE_DB185 defaults to "yes", but if you explicitly remove db1 from the list of acceptable DBs, then USE_DB185 defaults to "no". * Set BDB_LIBS to the library options needed to link against the DB library when bdb.buildlink3.mk is included. * We only add the DB library to the linker command automatically if we want DB-1.85 functionality; otherwise assume that the package configure process can figure out how to probe for the correct headers and libraries. Edit package Makefiles to nuke redundant settings of USE_DB185.
2004-11-15 18:54:49 +01:00
. if defined(USE_DB185) && !empty(USE_DB185:M[yY][eE][sS])
BUILDLINK_LIBS.db3= ${BUILDLINK_LDADD.db3}
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
2004-03-18 10:12:08 +01:00
BUILDLINK_TRANSFORM+= l:db:db3
. endif
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework.
2004-01-04 00:06:43 +01:00
.endif # DB3_BUILDLINK3_MK
Include "../../mk/pthread.buildlink3.mk"
2004-05-13 22:23:21 +02:00
.include "../../mk/pthread.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/+$//}
Reference in a new issue Copy permalink