diff options
| author | jlam <jlam> | 2001-06-29 05:07:36 +0000 |
|---|---|---|
| committer | jlam <jlam> | 2001-06-29 05:07:36 +0000 |
| commit | 1ddae6dad9846c6b62f871851ea344be1c56af7a (patch) | |
| tree | f3d746aa05b27b8ff5d7fc95b881e01e28800523 /Packages.txt | |
| parent | 7748c7e1a80c4e81c53ea9564bd97acb9a46125b (diff) | |
| download | pkgsrc-1ddae6dad9846c6b62f871851ea344be1c56af7a.tar.gz | |
Add new section: Converting packages to use buildlink.mk files. It needs
to be expanded, but what's there should help others to start using
buildlink.mk files.
Diffstat (limited to 'Packages.txt')
| -rw-r--r-- | Packages.txt | 30 |
1 files changed, 29 insertions, 1 deletions
diff --git a/Packages.txt b/Packages.txt index b30fad6aa19..dffe65740e1 100644 --- a/Packages.txt +++ b/Packages.txt @@ -1,4 +1,4 @@ -# $NetBSD: Packages.txt,v 1.166 2001/06/23 14:29:29 jlam Exp $ +# $NetBSD: Packages.txt,v 1.167 2001/06/29 05:07:36 jlam Exp $ ########################################################################### ========================== @@ -1571,6 +1571,34 @@ for a mythical package foo follows: > .include "../../mk/bsd.buildlink.mk" + 8.3 Converting packages to use buildlink.mk files + ================================================= + +The process of converting existing packages to use the buildlink.mk +infrastructure is fairly straightforward. If a dependency on a particular +package is required for its libraries and headers, then rather than +directly adding a dependency on that package, include that package's +buildlink.mk instead. The following variables may also be replaced with +buildlink.mk files: + + USE_CURSES --> .include "../../devel/ncurses/buildlink.mk" + USE_LIBINTL --> .include "../../devel/gettext-lib/buildlink.mk" + USE_LTDL --> .include "../../devel/libtool/buildlink.mk" + USE_MESA --> .include "../../graphics/Mesa/buildlink.mk" + USE_SSL --> .include "../../security/openssl/buildlink.mk" + USE_XPM --> .include "../../graphics/xpm/buildlink.mk" + +If the required dependency pattern for a package differs from the default +specified in the package's buildlink.mk file, then it may be set by +defining BUILDLINK_DEPENDS.<pkgname> in the Makefile to the dependency +pattern required. + +A package that builds correctly with USE_BUILDLINK_ONLY set should have +that setting added to its Makefile to note that it doesn't use any +libraries or headers in ${LOCALBASE} directly, but rather references them +only through ${BUILDLINK_DIR}. + + 9 Debugging =========== |