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

22 lines
775 B
Makefile
Raw Normal View History

Oy, what a hack. But then, so is Interix.... On Interix, force inclusion of devel/ncurses/buildlink3.mk from mk/curses.buildlink3.mk. This forces inclusion of its builtin.mk too. In devel/ncurses/builtin.mk, if using Interix's builtin ncurses, always transform -lncurses to -lcurses. (-lncurses is static, but -lcurses is shared; we want the shared version.)
2004-10-13 22:10:31 +02:00
# $NetBSD: curses.buildlink3.mk,v 1.3 2004/10/13 20:10:31 tv Exp $
curses.buildlink[23].mk files to be included by packages that use the curses library in some way. This file will automatically include ncurses/buildlink[23].mk if a curses implementation isn't available. If a package truly needs ncurses, then it should include ncurses/buildlink[23].mk directly.
2004-02-13 02:02:06 +01:00
#
# This file should be included by Makefiles for packages that use curses.
# If a system curses isn't available, then add a dependency on ncurses.
#
# If a package genuinely requires ncurses, then it should directly include
# ncurses/buildlink3.mk instead of this file in the package Makefile.
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
.if !exists(/usr/include/curses.h) && \
!exists(/usr/include/ncurses.h)
. include "../../devel/ncurses/buildlink3.mk"
Oy, what a hack. But then, so is Interix.... On Interix, force inclusion of devel/ncurses/buildlink3.mk from mk/curses.buildlink3.mk. This forces inclusion of its builtin.mk too. In devel/ncurses/builtin.mk, if using Interix's builtin ncurses, always transform -lncurses to -lcurses. (-lncurses is static, but -lcurses is shared; we want the shared version.)
2004-10-13 22:10:31 +02:00
.else
# XXX this is ugly, but needed to get the BUILDLINK_TRANSFORM from builtin.mk;
# on Interix, libncurses is static yet libcurses (also ncurses) is shared
. include "../../mk/bsd.prefs.mk"
. if ${OPSYS} == "Interix"
. include "../../devel/ncurses/buildlink3.mk"
. endif
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
.endif
Reference in a new issue Copy permalink