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

131 lines
4.3 KiB
Makefile
Raw Normal View History

resolve evaluate-undefined-variable issue for old bmake.
2014-03-12 09:38:47 +01:00
# $NetBSD: curses.buildlink3.mk,v 1.20 2014/03/12 08:38:47 obache 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
#
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
# This Makefile fragment is meant to be included by packages that require
# any curses implementation instead of one particular one. The available
# curses implementations are "curses" if built-in, "ncurses", and
# "pdcurses".
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
#
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
# If a package genuinely requires ncurses or pdcurses, then it should
# directly include the appropriate buildlink3.mk instead of this file in
# the package Makefile.
Clarified the comment.
2007-11-03 16:17:42 +01:00
#
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
# === User-settable variables ===
#
# CURSES_DEFAULT
# This value represents the type of curses we wish to use on the
# system. Setting this to "curses" means that the system curses
# implementation is fine.
#
Move the logic for testing if system curses supports the needed functions from devel/ncurses to the mk infrastructure. FAKE_NCURSES=yes Provides the system curses as ncurses.h and libncurses. USE_CURSES=wide Links to system curses if they provide wide support, otherwise ncursesw. wide-curses in the package options also triggers this.
2014-03-09 11:15:32 +01:00
# Possible: curses, ncurses, ncursesw, pdcurses
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
# Default: (depends)
#
# === Variables set by this file ===
#
# CURSES_TYPE
# The name of the selected curses implementation.
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
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
CURSES_BUILDLINK3_MK:= ${CURSES_BUILDLINK3_MK}+
.include "bsd.fast.prefs.mk"
.if !empty(CURSES_BUILDLINK3_MK:M+)
Move the logic for testing if system curses supports the needed functions from devel/ncurses to the mk infrastructure. FAKE_NCURSES=yes Provides the system curses as ncurses.h and libncurses. USE_CURSES=wide Links to system curses if they provide wide support, otherwise ncursesw. wide-curses in the package options also triggers this.
2014-03-09 11:15:32 +01:00
.if !defined(USE_CURSES) && !empty(PKG_OPTIONS:Mwide-curses)
USE_CURSES?= wide
.endif
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
# _CURSES_PKGS is an exhaustive list of all of the curses implementations
# that may be used with curses.buildlink3.mk.
#
Move the logic for testing if system curses supports the needed functions from devel/ncurses to the mk infrastructure. FAKE_NCURSES=yes Provides the system curses as ncurses.h and libncurses. USE_CURSES=wide Links to system curses if they provide wide support, otherwise ncursesw. wide-curses in the package options also triggers this.
2014-03-09 11:15:32 +01:00
_CURSES_PKGS?= curses ncurses ncursesw pdcurses
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
CHECK_BUILTIN.curses:= yes
. include "curses.builtin.mk"
CHECK_BUILTIN.curses:= no
# Set the value of CURSES_DEFAULT depending on the platform and what's
# available in the base system.
#
Allow preferring a pkgsrc "curses" implementation for all packages that include curses.buildlink3.mk. Generally, the rule is not to set CURSES_DEFAULT unless it's to set it to "ncurses" or "pdcurses". # Example mk.conf settings and their results. # Use the system curses. PREFER_NATIVE= yes # default value CURSES_DEFAULT= curses # default value # Use system "ncurses" if it's available, otherwise use devel/ncurses # from pkgsrc. # PREFER_NATIVE= yes # default value CURSES_DEFAULT= ncurses # Use devel/ncurses from pkgsrc. PREFER_PKGSRC= yes # Use devel/pdcurses from pkgsrc. PREFER_PKGSRC= yes CURSES_DEFAULT= pdcurses # This causes a package build failure because there is no pkgsrc # curses. # PREFER_PKGSRC= yes CURSES_DEFAULT= curses
2008-02-27 03:26:07 +01:00
.if defined(USE_BUILTIN.curses) && !empty(USE_BUILTIN.curses:M[yY][eE][sS])
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
CURSES_DEFAULT?= curses
resolve evaluate-undefined-variable issue for old bmake.
2014-03-12 09:38:47 +01:00
.elif !empty(USE_CURSES:U:Mwide) || !empty(PKG_OPTIONS:U:Mwide-curses)
Move the logic for testing if system curses supports the needed functions from devel/ncurses to the mk infrastructure. FAKE_NCURSES=yes Provides the system curses as ncurses.h and libncurses. USE_CURSES=wide Links to system curses if they provide wide support, otherwise ncursesw. wide-curses in the package options also triggers this.
2014-03-09 11:15:32 +01:00
CURSES_DEFAULT?= ncursesw
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
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
CURSES_DEFAULT?= ncurses
.endif
_CURSES_ACCEPTED= # empty
Allow preferring a pkgsrc "curses" implementation for all packages that include curses.buildlink3.mk. Generally, the rule is not to set CURSES_DEFAULT unless it's to set it to "ncurses" or "pdcurses". # Example mk.conf settings and their results. # Use the system curses. PREFER_NATIVE= yes # default value CURSES_DEFAULT= curses # default value # Use system "ncurses" if it's available, otherwise use devel/ncurses # from pkgsrc. # PREFER_NATIVE= yes # default value CURSES_DEFAULT= ncurses # Use devel/ncurses from pkgsrc. PREFER_PKGSRC= yes # Use devel/pdcurses from pkgsrc. PREFER_PKGSRC= yes CURSES_DEFAULT= pdcurses # This causes a package build failure because there is no pkgsrc # curses. # PREFER_PKGSRC= yes CURSES_DEFAULT= curses
2008-02-27 03:26:07 +01:00
.if defined(USE_BUILTIN.curses) && !empty(USE_BUILTIN.curses:M[yY][eE][sS])
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
_CURSES_ACCEPTED+= curses # system curses exists
.endif
Move the logic for testing if system curses supports the needed functions from devel/ncurses to the mk infrastructure. FAKE_NCURSES=yes Provides the system curses as ncurses.h and libncurses. USE_CURSES=wide Links to system curses if they provide wide support, otherwise ncursesw. wide-curses in the package options also triggers this.
2014-03-09 11:15:32 +01:00
.if defined(USE_BUILTIN.cursesw) && !empty(USE_BUILTIN.cursesw:M[yY][eE][sS])
_CURSES_ACCEPTED+= curses # system curses exists
.endif
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
_CURSES_ACCEPTED+= ncurses # pkgsrc ncurses
Move the logic for testing if system curses supports the needed functions from devel/ncurses to the mk infrastructure. FAKE_NCURSES=yes Provides the system curses as ncurses.h and libncurses. USE_CURSES=wide Links to system curses if they provide wide support, otherwise ncursesw. wide-curses in the package options also triggers this.
2014-03-09 11:15:32 +01:00
_CURSES_ACCEPTED+= ncursesw # pkgsrc ncursesw
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
_CURSES_ACCEPTED+= pdcurses # pkgsrc pdcurses
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
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
_CURSES_TYPE= ${CURSES_DEFAULT}
. if !empty(_CURSES_ACCEPTED:M${_CURSES_TYPE})
CURSES_TYPE= ${_CURSES_TYPE}
. else
CURSES_TYPE= none
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
. endif
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
BUILD_DEFS+= CURSES_DEFAULT
BUILD_DEFS_EFFECTS+= CURSES_TYPE
# _PKG_USE_CURSES is a flag for use by the curses packages' buildlink3.mk
# files to indicate that the headers and libraries should be usable as
# <curses.h> and -lcurses.
#
_PKG_USE_CURSES= yes
Move the logic for testing if system curses supports the needed functions from devel/ncurses to the mk infrastructure. FAKE_NCURSES=yes Provides the system curses as ncurses.h and libncurses. USE_CURSES=wide Links to system curses if they provide wide support, otherwise ncursesw. wide-curses in the package options also triggers this.
2014-03-09 11:15:32 +01:00
.PHONY: buildlink-curses-ncurses-h
buildlink-curses-ncurses-h:
${RUN} \
src="${H_CURSES}"; \
dest=${BUILDLINK_DIR}"/include/ncurses.h"; \
if ${TEST} ! -f "$$dest" -a -f "$$src"; then \
${ECHO_BUILDLINK_MSG} "Linking ${H_CURSES} -> ncurses.h.";\
${MKDIR} `${DIRNAME} "$$dest"`; \
${LN} -s "$$src" "$$dest"; \
fi
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
.endif # CURSES_BUILDLINK3_MK
.if ${CURSES_TYPE} == "none"
PKG_FAIL_REASON= \
"${_CURSES_TYPE} is not an acceptable curses type for ${PKGNAME}."
.elif ${CURSES_TYPE} == "curses"
Move the logic for testing if system curses supports the needed functions from devel/ncurses to the mk infrastructure. FAKE_NCURSES=yes Provides the system curses as ncurses.h and libncurses. USE_CURSES=wide Links to system curses if they provide wide support, otherwise ncursesw. wide-curses in the package options also triggers this.
2014-03-09 11:15:32 +01:00
. include "curses.builtin.mk"
Simply and speed up buildlink3.mk files and processing. This changes the buildlink3.mk files to use an include guard for the recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS, BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of enter/exit marker, which can be used to reconstruct the tree and to determine first level includes. Avoiding := for large variables (BUILDLINK_ORDER) speeds up parse time as += has linear complexity. The include guard reduces system time by avoiding reading files over and over again. For complex packages this reduces both %user and %sys time to half of the former time.
2009-03-20 20:23:50 +01:00
BUILDLINK_TREE+= curses -curses
If FOO is empty, then ${FOO:S/^/-l/} has a value of "-l". This is not what we want. Instead, use another pattern to strip away lone "-l" in BUILDLINK_LDADD.*.
2008-02-27 22:32:45 +01:00
BUILDLINK_LDADD.curses?= ${BUILDLINK_LIBNAME.curses:S/^/-l/:S/^-l$//}
Move the logic for testing if system curses supports the needed functions from devel/ncurses to the mk infrastructure. FAKE_NCURSES=yes Provides the system curses as ncurses.h and libncurses. USE_CURSES=wide Links to system curses if they provide wide support, otherwise ncursesw. wide-curses in the package options also triggers this.
2014-03-09 11:15:32 +01:00
BUSILDLINK_BUILTIN_MK.curses= ../../mk/curses.builtin.mk
# Some packages only look for ncurses
# The correct action would be to write a patch and pass it upstream
# but by setting FAKE_NCURSES=yes in the package we can temporarily work
# around the short-coming.
check FAKE_NCURSES is defined before evaluate it.
2014-03-10 13:57:03 +01:00
. if defined(FAKE_NCURSES) && !empty(FAKE_NCURSES:M[yY][eE][sS])
Move the logic for testing if system curses supports the needed functions from devel/ncurses to the mk infrastructure. FAKE_NCURSES=yes Provides the system curses as ncurses.h and libncurses. USE_CURSES=wide Links to system curses if they provide wide support, otherwise ncursesw. wide-curses in the package options also triggers this.
2014-03-09 11:15:32 +01:00
BUILDLINK_TARGETS+= buildlink-curses-ncurses-h
BUILDLINK_TRANSFORM+= l:ncurses:${BUILDLINK_LIBNAME.curses}
BUILDLINK_TRANSFORM+= l:ncursesw:${BUILDLINK_LIBNAME.curses}
. endif
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
.elif ${CURSES_TYPE} == "ncurses"
USE_NCURSES= yes
Fix another silly typo.
2010-02-07 11:28:13 +01:00
. include "../../devel/ncurses/buildlink3.mk"
Ensure that BUILDLINK_PREFIX.curses is always defined.
2008-02-29 17:29:04 +01:00
BUILDLINK_PREFIX.curses?= ${BUILDLINK_PREFIX.ncurses}
+ The termlib.buildlink3.mk file is meant to be included by packages that need basic termlib functionality, i.e. tgetent(), tgoto(), tputs(), etc. Together with the termlib.builtin.mk file, they will use either a built-in termcap library, a built-in X/Open "enhanced" curses library, or ncurses to provide these functions. + Add BUILDLINK_LIBNAME.* definitions to the various curses buildlink3.mk and builtin.mk files that give the "base" library name of the curses library, e.g. curses, ncurses, etc. These are used by the termlib files to set BUILDLINK_LIBNAME.termlib.
2008-02-27 05:47:02 +01:00
BUILDLINK_LIBNAME.curses?= ${BUILDLINK_LIBNAME.ncurses}
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
BUILDLINK_LDADD.curses?= ${BUILDLINK_LDADD.ncurses}
Move the logic for testing if system curses supports the needed functions from devel/ncurses to the mk infrastructure. FAKE_NCURSES=yes Provides the system curses as ncurses.h and libncurses. USE_CURSES=wide Links to system curses if they provide wide support, otherwise ncursesw. wide-curses in the package options also triggers this.
2014-03-09 11:15:32 +01:00
.elif ${CURSES_TYPE} == "ncursesw"
. include "../../devel/ncursesw/buildlink3.mk"
BUILDLINK_PREFIX.curses?= ${BUILDLINK_PREFIX.ncursesw}
BUILDLINK_LIBNAME.curses?= ${BUILDLINK_LIBNAME.ncursesw}
BUILDLINK_LDADD.curses?= ${BUILDLINK_LDADD.ncursesw}
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
.elif ${CURSES_TYPE} == "pdcurses"
. include "../../devel/pdcurses/buildlink3.mk"
Ensure that BUILDLINK_PREFIX.curses is always defined.
2008-02-29 17:29:04 +01:00
BUILDLINK_PREFIX.curses?= ${BUILDLINK_PREFIX.pdcurses}
+ The termlib.buildlink3.mk file is meant to be included by packages that need basic termlib functionality, i.e. tgetent(), tgoto(), tputs(), etc. Together with the termlib.builtin.mk file, they will use either a built-in termcap library, a built-in X/Open "enhanced" curses library, or ncurses to provide these functions. + Add BUILDLINK_LIBNAME.* definitions to the various curses buildlink3.mk and builtin.mk files that give the "base" library name of the curses library, e.g. curses, ncurses, etc. These are used by the termlib files to set BUILDLINK_LIBNAME.termlib.
2008-02-27 05:47:02 +01:00
BUILDLINK_LIBNAME.curses?= ${BUILDLINK_LIBNAME.pdcurses}
+ Introduce a way for a user to set the default curses implementation used by packages that need curses. From curses.buildlink3.mk: CURSES_DEFAULT This value represents the type of curses we wish to use on the system. Setting this to "curses" means that the system curses implementation is fine. Possible: curses, ncurses, pdcurses + Move all code to detect a built-in version of curses into a curses.builtin.mk file. + Add code to {n,pd}curses/buildlink3.mk so make the headers and libraries usable as <curses.h> and -lcurses if _PKG_USE_CURSES is defined. _PKG_USE_CURSES is only defined by curses.buildlink3.mk. + Improve the detection of native ncurses in ncurses/builtin.mk and allow headers and libraries to be usable as <ncurses.h> and -lncurses.
2008-02-25 05:19:34 +01:00
BUILDLINK_LDADD.curses?= ${BUILDLINK_LDADD.pdcurses}
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