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

211 lines
6.8 KiB
Makefile
Raw Normal View History

Extract .zst distfiles using archivers/zstd.
2022-01-06 11:19:11 +01:00
# $NetBSD: defaults.mk,v 1.63 2022/01/06 10:19:11 schmonz Exp $
Add TNF copyright to the new tools framework makefiles.
2005-05-21 06:46:52 +02:00
#
# Copyright (c) 2005 The NetBSD Foundation, Inc.
# All rights reserved.
#
# This code is derived from software contributed to The NetBSD Foundation
Grammar 101 -- sentences should end in a period.
2005-05-21 06:53:17 +02:00
# by Johnny C. Lam.
Add TNF copyright to the new tools framework makefiles.
2005-05-21 06:46:52 +02:00
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
# ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
# TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
# PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
# CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
# ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGE.
#
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
.if !defined(TOOLS_DEFAULTS_MK)
TOOLS_DEFAULTS_MK= defined
# These are the platform-specific lists of system-supplied tools.
#
# XXX These should eventually just migrate over to the appropriate
# XXX pkgsrc/mk/platform/${OPSYS}.mk file.
#
The mk/tools/defaults.mk is included by bsd.prefs.mk, so it must include other files without making assumptions about the location of the top of the pkgsrc tree. This fixes problems with running "make bulk-cache" in /usr/pkgsrc (PR pkg/30288).
2005-05-14 21:01:14 +02:00
.if exists(${_PKGSRC_TOPDIR}/mk/tools/tools.${OPSYS}.mk)
. include "${_PKGSRC_TOPDIR}/mk/tools/tools.${OPSYS}.mk"
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
.endif
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
######################################################################
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
# "TOOL" variable names associated with each of the tools
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.awk= AWK
_TOOLS_VARNAME.basename= BASENAME
Support bash as a tool, so that packages containing bash scripts (e.g. graphics/netpbm) use native bash if available.
2005-06-24 21:39:10 +02:00
_TOOLS_VARNAME.bash= BASH
Asking the tools framework for "bison" now provides two distinct tools: "bison" and "bison-yacc". bison is just a symlink to the real bison, but "bison-yacc" provides a "yacc" in ${TOOLS_DIR} that does "bison -y". This allows the tools framework to provide everything that a package might look for when asking for "bison" and avoids relying on the bison being available in the PATH.
2005-05-16 01:20:38 +02:00
_TOOLS_VARNAME.bison-yacc= YACC
Add 'printf' and 'byacc' variables corresponding to the new tools in replace.mk.
2005-11-04 20:27:13 +01:00
_TOOLS_VARNAME.byacc= YACC
Teach the new tools framework about USE_TOOLS+=bzcat.
2005-05-02 04:50:33 +02:00
_TOOLS_VARNAME.bzcat= BZCAT
Add bzip2 as tool. All platforms that had code to deal with bzcat also get bzip2, the rest falls back to archivers/bzip2. OK jlam.
2007-06-19 19:01:12 +02:00
_TOOLS_VARNAME.bzip2= BZIP2
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.cat= CAT
_TOOLS_VARNAME.chgrp= CHGRP
_TOOLS_VARNAME.chmod= CHMOD
_TOOLS_VARNAME.chown= CHOWN
Add support for cmake as a tool (USE_TOOLS+=cmake) and for using it in the configure stage of a build (by setting USE_CMAKE=yes).
2007-12-12 02:00:38 +01:00
_TOOLS_VARNAME.cmake= CMAKE
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.cmp= CMP
_TOOLS_VARNAME.cp= CP
Doing USE_TOOLS+=cmake in the configure stage is too late so move it to tools. Also cmake wants cpack to exist in the same directory so toolise it and make cmake and cpack imply each other.
2007-12-18 11:18:39 +01:00
_TOOLS_VARNAME.cpack= CPACK
Teach the tools framework about csh, and replace with tcsh if necessary.
2005-06-24 22:59:59 +02:00
_TOOLS_VARNAME.csh= CSH
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.cut= CUT
_TOOLS_VARNAME.date= DATE
Teach the tools framework about "diff".
2005-06-23 22:39:39 +02:00
_TOOLS_VARNAME.diff= DIFF
Add DIGEST to the variables defined by default.
2006-07-13 17:27:57 +02:00
_TOOLS_VARNAME.digest= DIGEST
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.dirname= DIRNAME
_TOOLS_VARNAME.echo= ECHO
_TOOLS_VARNAME.egrep= EGREP
_TOOLS_VARNAME.env= SETENV
_TOOLS_VARNAME.expr= EXPR
_TOOLS_VARNAME.false= FALSE
_TOOLS_VARNAME.fgrep= FGREP
_TOOLS_VARNAME.file= FILE_CMD
_TOOLS_VARNAME.find= FIND
_TOOLS_VARNAME.gawk= AWK
Teach how to unpack .gem files.
2006-10-15 03:56:06 +02:00
_TOOLS_VARNAME.gem= GEM
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.gm4= M4
_TOOLS_VARNAME.gmake= GMAKE
_TOOLS_VARNAME.grep= GREP
_TOOLS_VARNAME.gsed= SED
Teach the tools framework about "gsoelim", which is the soelim tool from a groff distribution.
2006-01-09 00:00:00 +01:00
_TOOLS_VARNAME.gsoelim= SOELIM
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.gtar= GTAR
_TOOLS_VARNAME.gunzip= GUNZIP_CMD
_TOOLS_VARNAME.gzcat= GZCAT
_TOOLS_VARNAME.gzip= GZIP_CMD
_TOOLS_VARNAME.head= HEAD
_TOOLS_VARNAME.hostname= HOSTNAME_CMD
_TOOLS_VARNAME.id= ID
Create IDENT variable by default.
2007-06-19 19:01:31 +02:00
_TOOLS_VARNAME.ident= IDENT
* Push the imake- and xmkmf-handling into the new tools framework. * Get rid of an explicit check for ${_IMAKE_MAKE} == ${GMAKE} in bsd.pkg.mk to check for whether we need to depend on gmake or not. Instead, we now note in Linux.mk that packages that need imake will also need to use gmake by setting _IMAKE_TOOLS+=gmake. * Push the definition of MAKE_PROGRAM from bsd.pkg.mk into make.mk where it's closer to related code.
2005-05-02 23:10:02 +02:00
_TOOLS_VARNAME.imake= IMAKE
Teach the new tools framework about INSTALL and set the appropriate default value for each platform. Currently, the replacement tools comes from sysutils/coreutils, but where there is no native BSD install program, bootstrap-pkgsrc should probably be made to provide an install shell script as an alternative, and mk/tools/bootstrap.mk should be amended accordingly. Also remove one use of ${TYPE} in pkgsrc (bsd.pkg.mk) under the new tools framework.
2005-05-03 22:41:53 +02:00
_TOOLS_VARNAME.install= INSTALL
Teach the tools framework how to supply a pkgsrc version of install-info if a native one isn't available. We ensure that the "install-info" tool in the tools directory is a no-op since the real info file registration is handled by the INSTALL/DEINSTALL script in pkgsrc/mk/pkginstall/install-info.
2006-03-06 06:25:45 +01:00
_TOOLS_VARNAME.install-info= INSTALL_INFO
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.lex= LEX
Teach the new tools framework about lha, unrar, unzip, and unzoo and modify bsd.pkg.extract.mk to use them. As a side-effect, we stop hardcoding ${LOCALBASE} as the install prefix for these tools so this becomes more pkgviews-friendly.
2005-05-14 00:08:20 +02:00
_TOOLS_VARNAME.lha= LHA
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.ln= LN
_TOOLS_VARNAME.ls= LS
Add lzcat to the tools framework. lzcat will be used to decompress .lzma files.
2008-11-15 21:20:44 +01:00
_TOOLS_VARNAME.lzcat= LZCAT
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.m4= M4
Teach the new tools framework about MAIL_CMD. We use mail/nail as a "mail" replacement in case TOOLS_PLATFORM.mail is empty.
2005-05-03 18:30:34 +02:00
_TOOLS_VARNAME.mail= MAIL_CMD
* Teach the tools framework how to supply the pkgsrc version of makeinfo if no native makeinfo executable exists. Honor TEXINFO_REQD when determining whether the native makeinfo can be used. * Remove USE_MAKEINFO and replace it with USE_TOOLS+=makeinfo. * Get rid of all the "split" argument deduction for makeinfo since the PLIST module already handles varying numbers of split info files correctly. NOTE: Platforms that have "makeinfo" in the base system should check that the makeinfo entries of pkgsrc/mk/tools.${OPSYS}.mk are correct.
2006-03-05 17:27:22 +01:00
_TOOLS_VARNAME.makeinfo= MAKEINFO
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.mkdir= MKDIR
Teach the tools framework about mktemp. Replace explicit tests for mktemp with USE_TOOLS+=mktemp in the samba packages.
2005-06-04 00:54:44 +02:00
_TOOLS_VARNAME.mktemp= MKTEMP
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.mtree= MTREE
_TOOLS_VARNAME.mv= MV
_TOOLS_VARNAME.nice= NICE
Teach the tools framework about nroff.
2005-05-26 23:46:13 +02:00
_TOOLS_VARNAME.nroff= NROFF
Teach the tools framework about "openssl".
2006-06-14 18:57:07 +02:00
_TOOLS_VARNAME.openssl= OPENSSL
Add 7z archive distfile support. Fix PR pkg/42967
2012-10-01 12:45:16 +02:00
_TOOLS_VARNAME.7za= P7ZA
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.patch= PATCH
_TOOLS_VARNAME.pax= PAX
Move perl handling into replace.mk. We now can specify USE_TOOLS+=perl to note that we need the perl binary and the associated PERL5 and TOOLS_PERL5 variable definitions.
2005-05-17 20:34:45 +02:00
_TOOLS_VARNAME.perl= PERL5
Provide a "pod2man" tool used by some packages to build man pages. Based on suggestion by Matthias Drochner.
2005-07-26 22:00:50 +02:00
_TOOLS_VARNAME.pod2man= POD2MAN
Add 'printf' and 'byacc' variables corresponding to the new tools in replace.mk.
2005-11-04 20:27:13 +01:00
_TOOLS_VARNAME.printf= PRINTF
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.pwd= PWD_CMD
_TOOLS_VARNAME.rm= RM
_TOOLS_VARNAME.rmdir= RMDIR
Give rpm2pkg a standard variable name "RPM2PKG" and teach GNU configure scripts about "cat".
2007-08-10 05:46:10 +02:00
_TOOLS_VARNAME.rpm2pkg= RPM2PKG
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.sed= SED
_TOOLS_VARNAME.sh= SH
_TOOLS_VARNAME.shlock= SHLOCK
Teach the tools framework about "sleep" which can be provided by the sysutils/coreutils package.
2005-11-04 21:02:01 +01:00
_TOOLS_VARNAME.sleep= SLEEP
Add "soelim", also part of groff if replacement is needed.
2005-11-08 04:36:13 +01:00
_TOOLS_VARNAME.soelim= SOELIM
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.sort= SORT
_TOOLS_VARNAME.tail= TAIL
Consider ${TAR} differently from ${GTAR}. Currently, mark pkgsrc down as needing both (no impact since they're both satisfied by the tar binary installed by the bootstrap kit). There's some funniness in the extraction code where we check for pax or GNU tar that needs to be resolved. Remove the TAR=${GTAR} hack since it's no longer needed after these changes. XXX Later, a sweep needs to be made to see where we actually need GTAR XXX and where we only need TAR, probably triggered by whether we call it XXX with the "z" option or not. Packages that need GTAR should explicitly XXX add USE_TOOLS+=gtar to the package Makefile.
2005-05-14 23:15:07 +02:00
_TOOLS_VARNAME.tar= TAR
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.tbl= TBL
Teach the tools framework about wish and tclsh, and set WISH and TCLSH accordingly for packages that need it.
2005-11-09 00:06:38 +01:00
_TOOLS_VARNAME.tclsh= TCLSH
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.tee= TEE
_TOOLS_VARNAME.test= TEST
_TOOLS_VARNAME.touch= TOUCH
_TOOLS_VARNAME.tr= TR
_TOOLS_VARNAME.true= TRUE
_TOOLS_VARNAME.tsort= TSORT
Provide uniq(1) as a TOOLS.
2014-03-06 08:34:20 +01:00
_TOOLS_VARNAME.uniq= UNIQ
Teach the new tools framework about lha, unrar, unzip, and unzoo and modify bsd.pkg.extract.mk to use them. As a side-effect, we stop hardcoding ${LOCALBASE} as the install prefix for these tools so this becomes more pkgviews-friendly.
2005-05-14 00:08:20 +02:00
_TOOLS_VARNAME.unrar= UNRAR
unzip uses UNZIP as a special environment variable to denote the options to pass to unzip. While this is stupid, it's still the reality, so we must not set UNZIP in the environment when calling unzip. Rename "UNZIP" to "UNZIP_CMD" to point to the path to the unzip binary.
2006-01-21 15:40:31 +01:00
_TOOLS_VARNAME.unzip= UNZIP_CMD
Teach the new tools framework about lha, unrar, unzip, and unzoo and modify bsd.pkg.extract.mk to use them. As a side-effect, we stop hardcoding ${LOCALBASE} as the install prefix for these tools so this becomes more pkgviews-friendly.
2005-05-14 00:08:20 +02:00
_TOOLS_VARNAME.unzoo= UNZOO
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.wc= WC
Teach the tools framework about wish and tclsh, and set WISH and TCLSH accordingly for packages that need it.
2005-11-09 00:06:38 +01:00
_TOOLS_VARNAME.wish= WISH
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.xargs= XARGS
* Push the imake- and xmkmf-handling into the new tools framework. * Get rid of an explicit check for ${_IMAKE_MAKE} == ${GMAKE} in bsd.pkg.mk to check for whether we need to depend on gmake or not. Instead, we now note in Linux.mk that packages that need imake will also need to use gmake by setting _IMAKE_TOOLS+=gmake. * Push the definition of MAKE_PROGRAM from bsd.pkg.mk into make.mk where it's closer to related code.
2005-05-02 23:10:02 +02:00
_TOOLS_VARNAME.xmkmf= XMKMF_CMD
fixes last commit (copy&paste error).
2013-12-01 03:57:36 +01:00
_TOOLS_VARNAME.xz= XZ
Add xzcat as a tool and update lzcat's TOOLS_DEPENDS to avoid conflicts. archivers/xz provides both lzcat and xzcat.
2009-07-08 14:51:16 +02:00
_TOOLS_VARNAME.xzcat= XZCAT
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
_TOOLS_VARNAME.yacc= YACC
Extract .zst distfiles using archivers/zstd.
2022-01-06 11:19:11 +01:00
_TOOLS_VARNAME.zstd= ZSTD
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
######################################################################
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
# "TOOL" variable names associated with each of the tools that are
# expected by GNU configure script.
_TOOLS_VARNAME_GNU.awk= AWK
_TOOLS_VARNAME_GNU.bison-yacc= YACC
Add a GNU variable for byacc so configure scripts will use YACC=byacc.
2005-11-04 20:28:33 +01:00
_TOOLS_VARNAME_GNU.byacc= YACC
Give rpm2pkg a standard variable name "RPM2PKG" and teach GNU configure scripts about "cat".
2007-08-10 05:46:10 +02:00
_TOOLS_VARNAME_GNU.cat= CAT ac_cv_path_CAT
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
_TOOLS_VARNAME_GNU.chmod= CHMOD
_TOOLS_VARNAME_GNU.cmp= CMP
_TOOLS_VARNAME_GNU.cp= CP
Teach the tools framework about "diff".
2005-06-23 22:39:39 +02:00
_TOOLS_VARNAME_GNU.diff= DIFF
Force an autoconf "cache" override for tools that are likely to be shell builtins, e.g. echo, false, test, true, since those tools don't have a full path.
2005-06-10 22:53:54 +02:00
_TOOLS_VARNAME_GNU.echo= ECHO ac_cv_path_ECHO
Work around brokenness in GNU configure scripts generated by autoconf-2.59a -- the checks for grep and egrep are broken because when passed GREP and EGREP in the environment, the script causes GREP and EGREP to be set to empty strings, which causes GNU configure scripts to hang or break. Pass the real paths to grep and egrep through using ac_cv_path_GREP and ac_cv_path_EGREP as well to avoid the brokenness. This fixes the build of textproc/gsed.
2005-05-23 19:07:22 +02:00
_TOOLS_VARNAME_GNU.egrep= EGREP ac_cv_path_EGREP
Add another common name for the GNU configure variable name used for the "env" tool.
2005-06-07 18:57:37 +02:00
_TOOLS_VARNAME_GNU.env= SETENV ENV_PROG ac_cv_path_ENV
Force an autoconf "cache" override for tools that are likely to be shell builtins, e.g. echo, false, test, true, since those tools don't have a full path.
2005-06-10 22:53:54 +02:00
_TOOLS_VARNAME_GNU.false= FALSE ac_cv_path_FALSE
Add a few more GNU configure variable names that are commonly used. Also, some configure scripts use "ENV" to represent the path to the "env" tool, which is probably bad since ENV has a special meaning to /bin/sh. To workaround this, set ac_cv_path_ENV.
2005-06-07 18:33:12 +02:00
_TOOLS_VARNAME_GNU.find= FIND
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
_TOOLS_VARNAME_GNU.gawk= AWK
_TOOLS_VARNAME_GNU.gm4= M4
Work around brokenness in GNU configure scripts generated by autoconf-2.59a -- the checks for grep and egrep are broken because when passed GREP and EGREP in the environment, the script causes GREP and EGREP to be set to empty strings, which causes GNU configure scripts to hang or break. Pass the real paths to grep and egrep through using ac_cv_path_GREP and ac_cv_path_EGREP as well to avoid the brokenness. This fixes the build of textproc/gsed.
2005-05-23 19:07:22 +02:00
_TOOLS_VARNAME_GNU.grep= GREP ac_cv_path_GREP
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
_TOOLS_VARNAME_GNU.gsed= SED
_TOOLS_VARNAME_GNU.gtar= TAR
_TOOLS_VARNAME_GNU.hostname= HOSTNAME
_TOOLS_VARNAME_GNU.lex= LEX
_TOOLS_VARNAME_GNU.ln= LN
Pull out the LS and TR definitions from algae/Makefile and place them in tools/defaults.mk where they can be more widely used.
2005-06-17 19:05:18 +02:00
_TOOLS_VARNAME_GNU.ls= LS
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
_TOOLS_VARNAME_GNU.m4= M4
Add a few more GNU configure variable names that are commonly used. Also, some configure scripts use "ENV" to represent the path to the "env" tool, which is probably bad since ENV has a special meaning to /bin/sh. To workaround this, set ac_cv_path_ENV.
2005-06-07 18:33:12 +02:00
_TOOLS_VARNAME_GNU.mkdir= MKDIR
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
_TOOLS_VARNAME_GNU.mv= MV
PERL_PATH is also a common GNU configure script variable for the path to the perl interpreter.
2005-06-17 18:24:51 +02:00
_TOOLS_VARNAME_GNU.perl= PERL PERL_PATH
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
_TOOLS_VARNAME_GNU.rm= RM
Add a few more GNU configure variable names that are commonly used. Also, some configure scripts use "ENV" to represent the path to the "env" tool, which is probably bad since ENV has a special meaning to /bin/sh. To workaround this, set ac_cv_path_ENV.
2005-06-07 18:33:12 +02:00
_TOOLS_VARNAME_GNU.rmdir= RMDIR
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
_TOOLS_VARNAME_GNU.sed= SED
Add a few more GNU configure variable names that are commonly used. Also, some configure scripts use "ENV" to represent the path to the "env" tool, which is probably bad since ENV has a special meaning to /bin/sh. To workaround this, set ac_cv_path_ENV.
2005-06-07 18:33:12 +02:00
_TOOLS_VARNAME_GNU.sort= SORT
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
_TOOLS_VARNAME_GNU.tar= TAR
Teach the tools framework about wish and tclsh, and set WISH and TCLSH accordingly for packages that need it.
2005-11-09 00:06:38 +01:00
_TOOLS_VARNAME_GNU.tclsh= TCLSH
Force an autoconf "cache" override for tools that are likely to be shell builtins, e.g. echo, false, test, true, since those tools don't have a full path.
2005-06-10 22:53:54 +02:00
_TOOLS_VARNAME_GNU.test= TEST ac_cv_path_TEST
Add a few more GNU configure variable names that are commonly used. Also, some configure scripts use "ENV" to represent the path to the "env" tool, which is probably bad since ENV has a special meaning to /bin/sh. To workaround this, set ac_cv_path_ENV.
2005-06-07 18:33:12 +02:00
_TOOLS_VARNAME_GNU.touch= TOUCH
Pull out the LS and TR definitions from algae/Makefile and place them in tools/defaults.mk where they can be more widely used.
2005-06-17 19:05:18 +02:00
_TOOLS_VARNAME_GNU.tr= TR
Force an autoconf "cache" override for tools that are likely to be shell builtins, e.g. echo, false, test, true, since those tools don't have a full path.
2005-06-10 22:53:54 +02:00
_TOOLS_VARNAME_GNU.true= TRUE ac_cv_path_TRUE
Teach the tools framework about wish and tclsh, and set WISH and TCLSH accordingly for packages that need it.
2005-11-09 00:06:38 +01:00
_TOOLS_VARNAME_GNU.wish= WISH
Add a few more tools for GNU configure scripts: grep, env, xmkmf.
2005-05-22 03:53:55 +02:00
_TOOLS_VARNAME_GNU.xmkmf= XMKMF
For packages that use GNU configure scripts, pass the real command paths for the tools that the package uses through the shell environment. We do this since these paths may be hardcoded into package scripts, and if they're not pre-specified, then they'll be searched for in the PATH, which would find the ones in ${TOOLS_DIR}. The variable names that GNU configure scripts expect are named in _TOOLS_VARNAME_GNU.* for the various tools.
2005-05-22 01:09:36 +02:00
_TOOLS_VARNAME_GNU.yacc= YACC
######################################################################
Drop distinction between PKGSRC_USE_TOOLS and USE_TOOLS by making PKGSRC_USE_TOOLS go away. There is now only a single USE_TOOLS variable that specifies all of the tools we need to build/run the package.
2005-07-15 20:27:48 +02:00
# Set a default value for the TOOL names for each of the tools we
# claim we'll use in USE_TOOLS to point to the platform command, e.g.,
Make a distinction between the tools that pkgsrc needs and the tools that a package needs. Tools that pkgsrc needs are listed in PKGSRC_USE_TOOLS, and tools that a package needs on top of that are listed in USE_TOOLS. Define "TOOL" variables, e.g. SED, AWK, MKDIR, etc. for each of the tools that pkgsrc needs, and "TOOLS_TOOL" variables, e.g. TOOLS_SED, TOOLS_AWK, TOOLS_MKDIR, etc. for each of the tools that a package needs. These variables contain the full command line to the real command and arguments needed to invoke the tool.
2005-05-10 21:06:58 +02:00
# TBL, YACC, etc. These tools are used in the top-level make(1), not
# just in the targets, so these must be defined here, and this file be
# included by bsd.prefs.mk.
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
#
Drop support for TOOLS_DEPMETHOD.<tool>. The new way to specify a run-time dependency (DEPENDS) on a tool is to append a ":run" modifier to the tool name, e.g., USE_TOOLS+= perl:run Tools without modifiers or with an explicit ":build" modifier will cause build dependencies (BUILD_DEPENDS) on those tools to be added. This makes the notation a bit more compact.
2005-07-15 22:14:02 +02:00
.for _t_ in ${USE_TOOLS:C/:.*//:O:u}
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
. if defined(_TOOLS_VARNAME.${_t_}) && \
defined(TOOLS_PLATFORM.${_t_}) && !empty(TOOLS_PLATFORM.${_t_})
Observe the following: VAR= a PTR= VAR ${PTR}?= b Given these definitions, ${VAR} == "b" (unintuitively). We can work around this by doing: VAR= a PTR= VAR .for _v_ in ${PTR} ${_v_}?= b .endfor In this case, ${VAR} == "a" (as expected). Use the second form of assignment in this changeset so that the expected behavior happens for the "TOOL" name variables. This fixes "recursively defined" errors for some of the "TOOL" variables when the pkgsrc tool replaces the system-supplied one.
2005-05-12 05:57:40 +02:00
. for _v_ in ${_TOOLS_VARNAME.${_t_}}
${_v_}?= ${TOOLS_PLATFORM.${_t_}}
. endfor
Split replace.mk into two parts, one of which is included by bsd.prefs.mk to provide "TOOL" definitions for tools used by a top-level make process (usually because it uses them in a != variable definition). This allows USE_TOOLS to be defined before bsd.prefs.mk is included by a package Makefile, where USE_TOOLS lists the additional (non-default) tools that are required to build the package. Also, drop the fallback to existing "TOOL" definitions because we now have TOOLS_PLATFORM.* for each platform in pkgsr/mk/tools/tools.*.mk.
2005-04-30 06:35:54 +02:00
. endif
.endfor
.endif # TOOLS_DEFAULTS_MK
Reference in a new issue Copy permalink