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

29 lines
813 B
Makefile
Raw Normal View History

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
# $NetBSD: buildlink3.mk,v 1.24 2006/07/08 23:10:39 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}+
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
DB_BUILDLINK3_MK:= ${DB_BUILDLINK3_MK}+
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework.
2004-01-04 00:06:43 +01:00
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
.if !empty(BUILDLINK_DEPTH:M+)
BUILDLINK_DEPENDS+= db2
Support a new global variable: BUILDLINK_PREFER_PKGSRC This variable determines whether or not to prefer the pkgsrc versions of software that is also present in the base system. This variable is multi-state: defined, or "yes" always prefer the pkgsrc versions not defined, or "no" only use the pkgsrc versions if needed by dependency requirements This can also take a list of packages for which to prefer the pkgsrc-installed software. The package names may be found by consulting the value added to BUILDLINK_PACKAGES in the buildlink[23].mk files for that package.
2004-02-05 07:58:02 +01:00
.endif
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
BUILDLINK_PACKAGES:= ${BUILDLINK_PACKAGES:Ndb2}
BUILDLINK_PACKAGES+= db2
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}db2
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework.
2004-01-04 00:06:43 +01:00
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
.if !empty(DB_BUILDLINK3_MK:M+)
Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-04-06 08:21:32 +02:00
BUILDLINK_API_DEPENDS.db2+= db>=2.7.3
BUILDLINK_ABI_DEPENDS.db2+= db>=2.7.7nb2
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
BUILDLINK_PKGSRCDIR.db2?= ../../databases/db
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.db2?= include/db2
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.db2= -ldb2
It suffices to load bsd.prefs.mk once.
2006-05-31 12:09:24 +02:00
. include "../../mk/bsd.prefs.mk"
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.db2= ${BUILDLINK_LDADD.db2}
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:db2
. endif
bdb.buildlink3.mk is used to select a Berkeley DB implementation for use by pkgsrc. It will automatically depend on either db, db3, or db4 if the native one isn't sufficient. The two variables that control its behaviour are: BDB_DEFAULT is a user-settable variable whose value is the default Berkeley DB implementation to use. BDB_ACCEPTED is a package-settable list of Berkeley DB implementations that may be used by the package. E.g., if you always want to use DB4 as the Berkeley DB for all of the packages, then you can just set: BDB_DEFAULT= db4 in your /etc/mk.conf. Packages that currently include db*/buildlink3.mk should be made to include bdb.buildlink3.mk instead.
2004-03-10 19:06:06 +01:00
.endif # DB_BUILDLINK3_MK
Initial sprinkling of work-in-progress buildlink3.mk files for using the buildlink3 framework.
2004-01-04 00:06:43 +01:00
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/+$//}
Reference in a new issue Copy permalink