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

841 lines
29 KiB
Makefile
Raw Normal View History

* 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
# $NetBSD: replace.mk,v 1.57 2005/05/02 21:10:03 jlam Exp $
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
#
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
# This Makefile fragment handles "replacements" of system-supplied
# tools with pkgsrc versions. The replacements are placed under
# ${TOOLS_DIR} so that they appear earlier in the search path when
# invoked using the bare name of the tool. Also, any "TOOL" variables,
# e.g. AWK, SED, etc. are set properly to the replacement tool.
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
#
# The tools that could be replaced with pkgsrc counterparts (usually
# GNU versions of the tools) should be listed in each package Makefile
# as:
#
Rename "awk" to "gawk" to make it more explicit that we want GNU awk (probably for gensub() ).
2005-04-25 00:34:35 +02:00
# USE_TOOLS+= gawk gmake lex
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
#
# If a package requires yacc to generate a parser, then the package
# Makefile should contain one of the following two lines:
#
# USE_TOOLS+= yacc # any yacc will do
# USE_TOOLS+= bison # requires bison-specific features
#
# Adding either "yacc" or "bison" to USE_TOOLS will cause a "yacc" tool
# to be generated that may be used as a yacc-replacement.
#
Allow TOOLS_DEPENDS.<tool> to be set to change the nature of the dependency if we're using the pkgsrc tool, e.g. TOOL_DEPENDS.yacc=DEPENDS. By default, we use BUILD_DEPENDS.
2005-04-15 08:52:25 +02:00
# By default, any dependencies on the pkgsrc tools are build dependencies,
Rename TOOLS_DEPENDS.* to TOOLS_DEPMETHOD.* to roughly match the buildlink terminology for the same concept.
2005-04-28 04:10:56 +02:00
# but this may be changed by explicitly setting TOOLS_DEPMETHOD.<tool>,
Allow TOOLS_DEPENDS.<tool> to be set to change the nature of the dependency if we're using the pkgsrc tool, e.g. TOOL_DEPENDS.yacc=DEPENDS. By default, we use BUILD_DEPENDS.
2005-04-15 08:52:25 +02:00
# e.g.:
#
Rename TOOLS_DEPENDS.* to TOOLS_DEPMETHOD.* to roughly match the buildlink terminology for the same concept.
2005-04-28 04:10:56 +02:00
# TOOLS_DEPMETHOD.tbl= DEPENDS
Allow TOOLS_DEPENDS.<tool> to be set to change the nature of the dependency if we're using the pkgsrc tool, e.g. TOOL_DEPENDS.yacc=DEPENDS. By default, we use BUILD_DEPENDS.
2005-04-15 08:52:25 +02:00
#
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
# Continue to allow USE_GNU_TOOLS and USE_TBL until packages have been
# taught to use the new syntax.
#
Avoid using a for loop (optimization) which also broke when using the bootstrap bmake.
2005-04-22 04:29:28 +02:00
.if defined(USE_GNU_TOOLS) && !empty(USE_GNU_TOOLS)
Rename the "sed" option for USE_TOOLS to "gsed" to note that we want GNU sed.
2005-04-26 21:11:25 +02:00
USE_TOOLS+= ${USE_GNU_TOOLS:S/^awk$/gawk/:S/^make$/gmake/:S/^sed$/gsed/}
Avoid using a for loop (optimization) which also broke when using the bootstrap bmake.
2005-04-22 04:29:28 +02:00
.endif
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
.if defined(USE_TBL) && !empty(USE_TBL:M[yY][eE][sS])
USE_TOOLS+= tbl
.endif
* 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
.include "../../mk/tools/imake.mk"
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
######################################################################
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
# Create _USE_TOOLS, a sanitized version of USE_TOOLS that removes the
# tools that are overridden by superseding ones.
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
_USE_TOOLS:= ${USE_TOOLS:O:u}
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !empty(USE_TOOLS:Mbison) # bison > yacc
_USE_TOOLS:= ${_USE_TOOLS:Nyacc}
.endif
.if !empty(USE_TOOLS:Mgawk) # gawk > awk
_USE_TOOLS:= ${_USE_TOOLS:Nawk}
.endif
.if !empty(USE_TOOLS:Mgm4) # gm4 > m4
_USE_TOOLS:= ${_USE_TOOLS:Nm4}
.endif
.if !empty(USE_TOOLS:Mgsed) # gsed > sed
_USE_TOOLS:= ${_USE_TOOLS:Nsed}
.endif
######################################################################
If PLATFORM_TOOL.<tool> is defined for a particular tool, then use it instead of the pkgsrc version of the tool. This is an alternative to adding the appropriate platform to the _TOOLS_USE_PLATFORM.* tables.
2005-04-25 08:16:38 +02:00
# _TOOLS_USE_PKGSRC.<tool> is "yes" or "no" depending on whether we're
# using a pkgsrc-supplied tool to replace the system-supplied one. We
Rename PLATFORM_TOOLS.* to TOOLS_PLATFORM.* to bring the variable names under the same namespace as the other parts of the new tools framework.
2005-04-27 18:52:28 +02:00
# use the system-supplied one if TOOLS_PLATFORM.<tool> is non-empty, or
If PLATFORM_TOOL.<tool> is defined for a particular tool, then use it instead of the pkgsrc version of the tool. This is an alternative to adding the appropriate platform to the _TOOLS_USE_PLATFORM.* tables.
2005-04-25 08:16:38 +02:00
# otherwise if this is a particular ${MACHINE_PLATFORM} listed above.
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
#
We only need to loop over the tools that we say we're going to use.
2005-04-28 17:51:10 +02:00
.for _t_ in ${_USE_TOOLS}
Rename PLATFORM_TOOLS.* to TOOLS_PLATFORM.* to bring the variable names under the same namespace as the other parts of the new tools framework.
2005-04-27 18:52:28 +02:00
. if defined(TOOLS_PLATFORM.${_t_}) && !empty(TOOLS_PLATFORM.${_t_})
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
_TOOLS_USE_PKGSRC.${_t_}?= no
Get rid of the _TOOLS_USE_PLATFORM.* table as the information has now been placed in the various tools.${OPSYS}.mk files using PLATFORM_TOOL.* definitions.
2005-04-27 18:02:08 +02:00
. endif
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
_TOOLS_USE_PKGSRC.${_t_}?= yes
.endfor
.undef _t_
Rename TOOLS_DEPENDS.* to TOOLS_DEPMETHOD.* to roughly match the buildlink terminology for the same concept.
2005-04-28 04:10:56 +02:00
# TOOLS_DEPMETHOD.<tool> defaults to BUILD_DEPENDS.
We only need to loop over the tools that we say we're going to use.
2005-04-28 17:51:10 +02:00
.for _t_ in ${_USE_TOOLS}
Rename TOOLS_DEPENDS.* to TOOLS_DEPMETHOD.* to roughly match the buildlink terminology for the same concept.
2005-04-28 04:10:56 +02:00
TOOLS_DEPMETHOD.${_t_}?= BUILD_DEPENDS
Allow TOOLS_DEPENDS.<tool> to be set to change the nature of the dependency if we're using the pkgsrc tool, e.g. TOOL_DEPENDS.yacc=DEPENDS. By default, we use BUILD_DEPENDS.
2005-04-15 08:52:25 +02:00
.endfor
.undef _t_
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
######################################################################
# For each of the blocks below, we create either symlinks or wrappers
# for each of the tools requested. We need to be careful that we don't
# get into dependency loops; do this by setting and checking the value
# of TOOLS_IGNORE.<tool>. If we're using the system-supplied tool, we
# defer the setting of TOOLS_REAL_CMD.<tool> until the loop at the end.
Remove conflict between bison and yacc... now "bison" simply overrides "yacc" when both are specified. Also add comments to note other instances where we override other tools: gsed & sed, gawk & awk, gm4 & m4.
2005-04-27 18:41:11 +02:00
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.[) && !empty(_USE_TOOLS:M\[)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.[=
. elif !empty(_TOOLS_USE_PKGSRC.[:M[yY][eE][sS])
TOOLS_DEPENDS.[?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= [
TOOLS_REAL_CMD.[= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}[
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.awk) && !empty(_USE_TOOLS:Mawk)
Teach replace.mk about awk, m4, and sed when the GNU versions aren't required.
2005-04-27 18:28:19 +02:00
. if !empty(PKGPATH:Mlang/gawk)
MAKEFLAGS+= TOOLS_IGNORE.awk=
. elif !empty(_TOOLS_USE_PKGSRC.awk:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.awk?= gawk>=3.1.1:../../lang/gawk
Teach replace.mk about awk, m4, and sed when the GNU versions aren't required.
2005-04-27 18:28:19 +02:00
TOOLS_SYMLINK+= awk
TOOLS_REAL_CMD.awk= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}awk
${_TOOLS_VARNAME.awk}= ${TOOLS_REAL_CMD.awk}
. endif
.endif
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.basename) && !empty(_USE_TOOLS:Mbasename)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.basename=
. elif !empty(_TOOLS_USE_PKGSRC.basename:M[yY][eE][sS])
TOOLS_DEPENDS.basename?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= basename
TOOLS_REAL_CMD.basename= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}basename
${_TOOLS_VARNAME.basename}= ${TOOLS_REAL_CMD.basename}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.bison) && !empty(_USE_TOOLS:Mbison)
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
. if !empty(PKGPATH:Mdevel/bison)
MAKEFLAGS+= TOOLS_IGNORE.bison=
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
. elif !empty(_TOOLS_USE_PKGSRC.bison:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.bison?= bison>=1.0:../../devel/bison
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
TOOLS_WRAP+= bison
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
TOOLS_REAL_CMD.bison= ${LOCALBASE}/bin/bison
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
TOOLS_ARGS.bison= -y
${_TOOLS_VARNAME.bison}= ${TOOLS_REAL_CMD.bison} ${TOOLS_ARGS.bison}
. endif
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
TOOLS_CMD.bison= ${TOOLS_DIR}/bin/yacc
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
.endif
Teach the new tools framework about USE_TOOLS+=bzcat.
2005-05-02 04:50:33 +02:00
.if !defined(TOOLS_IGNORE.bzcat) && !empty(_USE_TOOLS:Mbzcat)
. if !empty(PKGPATH:Marchivers/bzip2)
MAKEFLAGS+= TOOLS_IGNORE.bzcat=
. elif !empty(_TOOLS_USE_PKGSRC.bzcat:M[yY][eE][sS])
TOOLS_DEPENDS.bzcat?= bzip2>=0.9.0b:../../archivers/bzip2
TOOLS_SYMLINK+= bzcat
TOOLS_REAL_CMD.bzcat= ${LOCALBASE}/bin/bzcat
${_TOOLS_VARNAME.bzcat}= ${TOOLS_REAL_CMD.bzcat}
. endif
.endif
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.cat) && !empty(_USE_TOOLS:Mcat)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.cat=
. elif !empty(_TOOLS_USE_PKGSRC.cat:M[yY][eE][sS])
TOOLS_DEPENDS.cat?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= cat
TOOLS_REAL_CMD.cat= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}cat
${_TOOLS_VARNAME.cat}= ${TOOLS_REAL_CMD.cat}
. endif
.endif
.if !defined(TOOLS_IGNORE.chgrp) && !empty(_USE_TOOLS:Mchgrp)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.chgrp=
. elif !empty(_TOOLS_USE_PKGSRC.chgrp:M[yY][eE][sS])
TOOLS_DEPENDS.chgrp?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= chgrp
TOOLS_REAL_CMD.chgrp= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}chgrp
${_TOOLS_VARNAME.chgrp}= ${TOOLS_REAL_CMD.chgrp}
. endif
.endif
.if !defined(TOOLS_IGNORE.chmod) && !empty(_USE_TOOLS:Mchmod)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.chmod=
. elif !empty(_TOOLS_USE_PKGSRC.chmod:M[yY][eE][sS])
TOOLS_DEPENDS.chmod?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= chmod
TOOLS_REAL_CMD.chmod= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}chmod
${_TOOLS_VARNAME.chmod}= ${TOOLS_REAL_CMD.chmod}
. endif
.endif
.if !defined(TOOLS_IGNORE.chown) && !empty(_USE_TOOLS:Mchown)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.chown=
. elif !empty(_TOOLS_USE_PKGSRC.chown:M[yY][eE][sS])
TOOLS_DEPENDS.chown?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= chown
TOOLS_REAL_CMD.chown= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}chown
${_TOOLS_VARNAME.chown}= ${TOOLS_REAL_CMD.chown}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.cmp) && !empty(_USE_TOOLS:Mcmp)
Teach replace.mk about cmp/CMP.
2005-04-27 01:20:35 +02:00
. if !empty(PKGPATH:Mdevel/diffutils)
MAKEFLAGS+= TOOLS_IGNORE.cmp=
. elif !empty(_TOOLS_USE_PKGSRC.cmp:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.cmp?= diffutils>=2.8.1:../../devel/diffutils
cmp should be a symlink, not a wrapper.
2005-04-27 18:29:45 +02:00
TOOLS_SYMLINK+= cmp
Teach replace.mk about cmp/CMP.
2005-04-27 01:20:35 +02:00
TOOLS_REAL_CMD.cmp= ${LOCALBASE}/bin/cmp
${_TOOLS_VARNAME.cmp}= ${TOOLS_REAL_CMD.cmp}
. endif
.endif
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.cp) && !empty(_USE_TOOLS:Mcp)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.cp=
. elif !empty(_TOOLS_USE_PKGSRC.cp:M[yY][eE][sS])
TOOLS_DEPENDS.cp?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= cp
TOOLS_REAL_CMD.cp= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}cp
${_TOOLS_VARNAME.cp}= ${TOOLS_REAL_CMD.cp}
. endif
.endif
.if !defined(TOOLS_IGNORE.cut) && !empty(_USE_TOOLS:Mcut)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.cut=
. elif !empty(_TOOLS_USE_PKGSRC.cut:M[yY][eE][sS])
TOOLS_DEPENDS.cut?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= cut
TOOLS_REAL_CMD.cut= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}cut
${_TOOLS_VARNAME.cut}= ${TOOLS_REAL_CMD.cut}
. endif
.endif
.if !defined(TOOLS_IGNORE.date) && !empty(_USE_TOOLS:Mdate)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.date=
. elif !empty(_TOOLS_USE_PKGSRC.date:M[yY][eE][sS])
TOOLS_DEPENDS.date?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= date
TOOLS_REAL_CMD.date= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}date
${_TOOLS_VARNAME.date}= ${TOOLS_REAL_CMD.date}
. endif
.endif
.if !defined(TOOLS_IGNORE.dirname) && !empty(_USE_TOOLS:Mdirname)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.dirname=
. elif !empty(_TOOLS_USE_PKGSRC.dirname:M[yY][eE][sS])
TOOLS_DEPENDS.dirname?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= dirname
TOOLS_REAL_CMD.dirname= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}dirname
${_TOOLS_VARNAME.dirname}= ${TOOLS_REAL_CMD.dirname}
. endif
.endif
.if !defined(TOOLS_IGNORE.echo) && !empty(_USE_TOOLS:Mecho)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.echo=
. elif !empty(_TOOLS_USE_PKGSRC.echo:M[yY][eE][sS])
TOOLS_DEPENDS.echo?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= echo
TOOLS_REAL_CMD.echo= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}echo
${_TOOLS_VARNAME.echo}= ${TOOLS_REAL_CMD.echo}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.egrep) && !empty(_USE_TOOLS:Megrep)
Sort the tool-specific sections for easier browsing.
2005-04-26 21:15:38 +02:00
. if !empty(PKGPATH:Mtextproc/grep)
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
MAKEFLAGS+= TOOLS_IGNORE.egrep=
. elif !empty(_TOOLS_USE_PKGSRC.egrep:M[yY][eE][sS])
TOOLS_DEPENDS.egrep?= grep>=2.5.1:../../textproc/grep
TOOLS_SYMLINK+= egrep
TOOLS_REAL_CMD.egrep= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}egrep
${_TOOLS_VARNAME.egrep}= ${TOOLS_REAL_CMD.egrep}
. endif
.endif
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.env) && !empty(_USE_TOOLS:Menv)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.env=
. elif !empty(_TOOLS_USE_PKGSRC.env:M[yY][eE][sS])
TOOLS_DEPENDS.env?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= env
TOOLS_REAL_CMD.env= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}env
${_TOOLS_VARNAME.env}= ${TOOLS_REAL_CMD.env}
. endif
.endif
.if !defined(TOOLS_IGNORE.expr) && !empty(_USE_TOOLS:Mexpr)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.expr=
. elif !empty(_TOOLS_USE_PKGSRC.expr:M[yY][eE][sS])
TOOLS_DEPENDS.expr?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= expr
TOOLS_REAL_CMD.expr= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}expr
${_TOOLS_VARNAME.expr}= ${TOOLS_REAL_CMD.expr}
. endif
.endif
.if !defined(TOOLS_IGNORE.false) && !empty(_USE_TOOLS:Mfalse)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.false=
. elif !empty(_TOOLS_USE_PKGSRC.false:M[yY][eE][sS])
TOOLS_DEPENDS.false?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= false
TOOLS_REAL_CMD.false= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}false
${_TOOLS_VARNAME.false}= ${TOOLS_REAL_CMD.false}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.fgrep) && !empty(_USE_TOOLS:Mfgrep)
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
. if !empty(PKGPATH:Mtextproc/grep)
MAKEFLAGS+= TOOLS_IGNORE.fgrep=
. elif !empty(_TOOLS_USE_PKGSRC.fgrep:M[yY][eE][sS])
TOOLS_DEPENDS.fgrep?= grep>=2.5.1:../../textproc/grep
TOOLS_SYMLINK+= fgrep
TOOLS_REAL_CMD.fgrep= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}fgrep
${_TOOLS_VARNAME.fgrep}= ${TOOLS_REAL_CMD.fgrep}
Sort the tool-specific sections for easier browsing.
2005-04-26 21:15:38 +02:00
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.file) && !empty(_USE_TOOLS:Mfile)
Teach replace.mk about egrep, fgrep, and file.
2005-04-15 18:01:23 +02:00
. if !empty(PKGPATH:Msysutils/file)
MAKEFLAGS+= TOOLS_IGNORE.file=
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
. elif !empty(_TOOLS_USE_PKGSRC.file:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.file?= file>=4.13:../../sysutils/file
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
TOOLS_SYMLINK+= file
Teach replace.mk about egrep, fgrep, and file.
2005-04-15 18:01:23 +02:00
TOOLS_REAL_CMD.file= ${LOCALBASE}/bin/file
${_TOOLS_VARNAME.file}= ${TOOLS_REAL_CMD.file}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.find) && !empty(_USE_TOOLS:Mfind)
Merge findutils.mk into replace.mk. We now just use USE_TOOLS+=find or USE_TOOLS+=xargs, and cause FIND and XARGS to point to the correct commands.
2005-04-27 00:28:03 +02:00
. if !empty(PKGPATH:Msysutils/findutils)
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
MAKEFLAGS+= TOOLS_IGNORE.find=
. elif !empty(_TOOLS_USE_PKGSRC.find:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.find?= findutils>=4.1:../../sysutils/findutils
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
TOOLS_SYMLINK+= find
TOOLS_REAL_CMD.find= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}find
${_TOOLS_VARNAME.find}= ${TOOLS_REAL_CMD.find}
Merge findutils.mk into replace.mk. We now just use USE_TOOLS+=find or USE_TOOLS+=xargs, and cause FIND and XARGS to point to the correct commands.
2005-04-27 00:28:03 +02:00
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.gawk) && !empty(_USE_TOOLS:Mgawk)
Rename "awk" to "gawk" to make it more explicit that we want GNU awk (probably for gensub() ).
2005-04-25 00:34:35 +02:00
. if !empty(PKGPATH:Mlang/gawk)
MAKEFLAGS+= TOOLS_IGNORE.gawk=
. elif !empty(_TOOLS_USE_PKGSRC.gawk:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.gawk?= gawk>=3.1.1:../../lang/gawk
Rename "awk" to "gawk" to make it more explicit that we want GNU awk (probably for gensub() ).
2005-04-25 00:34:35 +02:00
TOOLS_SYMLINK+= gawk
TOOLS_REAL_CMD.gawk= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}awk
${_TOOLS_VARNAME.gawk}= ${TOOLS_REAL_CMD.gawk}
. endif
The gawk and gsed tools are called "awk" and "sed" under ${TOOLS_DIR} since that's how most applications expect to invoke awk and sed.
2005-04-26 21:14:42 +02:00
TOOLS_CMD.gawk= ${TOOLS_DIR}/bin/awk
Rename "awk" to "gawk" to make it more explicit that we want GNU awk (probably for gensub() ).
2005-04-25 00:34:35 +02:00
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.gm4) && !empty(_USE_TOOLS:Mgm4)
Rename "m4" to "gm4" to more explicitly note that we want GNU m4. The tool name under ${TOOLS_DIR} is still "m4".
2005-04-25 00:42:00 +02:00
. if !empty(PKGPATH:Mdevel/m4)
MAKEFLAGS+= TOOLS_IGNORE.gm4=
. elif !empty(_TOOLS_USE_PKGSRC.gm4:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.gm4?= m4>=1.4:../../devel/m4
Rename "m4" to "gm4" to more explicitly note that we want GNU m4. The tool name under ${TOOLS_DIR} is still "m4".
2005-04-25 00:42:00 +02:00
TOOLS_SYMLINK+= gm4
TOOLS_REAL_CMD.gm4= ${LOCALBASE}/bin/gm4
${_TOOLS_VARNAME.gm4}= ${TOOLS_REAL_CMD.gm4}
. endif
Packages that want GNU m4 will probably still invoke it as "m4".
2005-04-27 00:31:34 +02:00
TOOLS_CMD.gm4= ${TOOLS_DIR}/bin/m4
Rename "m4" to "gm4" to more explicitly note that we want GNU m4. The tool name under ${TOOLS_DIR} is still "m4".
2005-04-25 00:42:00 +02:00
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.gmake) && !empty(_USE_TOOLS:Mgmake)
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
. if !empty(PKGPATH:Mdevel/gmake)
MAKEFLAGS+= TOOLS_IGNORE.gmake=
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
. elif !empty(_TOOLS_USE_PKGSRC.gmake:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.gmake?= gmake>=3.78:../../devel/gmake
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
TOOLS_SYMLINK+= gmake
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
TOOLS_REAL_CMD.gmake= ${LOCALBASE}/bin/gmake
${_TOOLS_VARNAME.gmake}= ${TOOLS_REAL_CMD.gmake}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.grep) && !empty(_USE_TOOLS:Mgrep)
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
. if !empty(PKGPATH:Mtextproc/grep)
MAKEFLAGS+= TOOLS_IGNORE.grep=
. elif !empty(_TOOLS_USE_PKGSRC.grep:M[yY][eE][sS])
TOOLS_DEPENDS.grep?= grep>=2.5.1:../../textproc/grep
TOOLS_SYMLINK+= grep
TOOLS_REAL_CMD.grep= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}grep
${_TOOLS_VARNAME.grep}= ${TOOLS_REAL_CMD.grep}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.gsed) && !empty(_USE_TOOLS:Mgsed)
Correct the PKGPATH for gsed.
2005-04-28 06:00:15 +02:00
. if !empty(PKGPATH:Mtextproc/gsed)
Sort the tool-specific sections for easier browsing.
2005-04-26 21:15:38 +02:00
MAKEFLAGS+= TOOLS_IGNORE.gsed=
. elif !empty(_TOOLS_USE_PKGSRC.gsed:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.gsed?= gsed>=3.0.2:../../textproc/gsed
Sort the tool-specific sections for easier browsing.
2005-04-26 21:15:38 +02:00
TOOLS_SYMLINK+= gsed
TOOLS_REAL_CMD.gsed= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}sed
${_TOOLS_VARNAME.gsed}= ${TOOLS_REAL_CMD.gsed}
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
. endif
Sort the tool-specific sections for easier browsing.
2005-04-26 21:15:38 +02:00
TOOLS_CMD.gsed= ${TOOLS_DIR}/bin/sed
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.gtar) && !empty(_USE_TOOLS:Mgtar)
Teach replace.mk about GTAR and PAX (replace with archivers/pax if necessary).
2005-04-27 05:41:17 +02:00
. if !empty(PKGPATH:Marchivers/pax)
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
MAKEFLAGS+= TOOLS_IGNORE.gtar=
. elif !empty(_TOOLS_USE_PKGSRC.gtar:M[yY][eE][sS])
We can't add dependencies on packages that are never registered. archivers/pax and pkgtools/mtree fall in this category since they are usually installed by pkgsrc bootstrap.
2005-04-27 17:21:50 +02:00
#
# This is installed by pkgsrc bootstrap, and is never registered, so
# comment out the dependency on it.
#
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
#TOOLS_DEPENDS.gtar?= pax>=20040802:../../archivers/pax
TOOLS_SYMLINK+= gtar
Teach replace.mk about GTAR and PAX (replace with archivers/pax if necessary).
2005-04-27 05:41:17 +02:00
TOOLS_REAL_CMD.gtar= ${LOCALBASE}/bin/tar
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
${_TOOLS_VARNAME.gtar}= ${TOOLS_REAL_CMD.gtar}
Teach replace.mk about GTAR and PAX (replace with archivers/pax if necessary).
2005-04-27 05:41:17 +02:00
. endif
TOOLS_CMD.gtar= ${TOOLS_DIR}/bin/tar
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.gunzip) && !empty(_USE_TOOLS:Mgunzip)
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
. if !empty(PKGPATH:Marchivers/gzip)
MAKEFLAGS+= TOOLS_IGNORE.gunzip=
. elif !empty(_TOOLS_USE_PKGSRC.gunzip:M[yY][eE][sS])
TOOLS_DEPENDS.gunzip?= gzip-base>=1.2.4b:../../archivers/gzip-base
TOOLS_SYMLINK+= gunzip
TOOLS_REAL_CMD.gunzip= ${LOCALBASE}/bin/gunzip
${_TOOLS_VARNAME.gunzip}= ${TOOLS_REAL_CMD.gunzip}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.gzcat) && !empty(_USE_TOOLS:Mgzcat)
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
. if !empty(PKGPATH:Marchivers/gzip)
MAKEFLAGS+= TOOLS_IGNORE.gzcat=
. elif !empty(_TOOLS_USE_PKGSRC.gzcat:M[yY][eE][sS])
TOOLS_DEPENDS.gzcat?= gzip-base>=1.2.4b:../../archivers/gzip-base
TOOLS_SYMLINK+= gzcat
TOOLS_REAL_CMD.gzcat= ${LOCALBASE}/bin/gzcat
${_TOOLS_VARNAME.gzcat}= ${TOOLS_REAL_CMD.gzcat}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.gzip) && !empty(_USE_TOOLS:Mgzip)
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
. if !empty(PKGPATH:Marchivers/gzip)
MAKEFLAGS+= TOOLS_IGNORE.gzip=
. elif !empty(_TOOLS_USE_PKGSRC.gzip:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.gzip?= gzip-base>=1.2.4b:../../archivers/gzip-base
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
TOOLS_SYMLINK+= gzip
TOOLS_REAL_CMD.gzip= ${LOCALBASE}/bin/gzip
${_TOOLS_VARNAME.gzip}= ${TOOLS_REAL_CMD.gzip}
Teach replace.mk about gzip, gunzip, and gzcat.
2005-04-24 05:59:44 +02:00
. endif
.endif
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.head) && !empty(_USE_TOOLS:Mhead)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.head=
. elif !empty(_TOOLS_USE_PKGSRC.head:M[yY][eE][sS])
TOOLS_DEPENDS.head?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= head
TOOLS_REAL_CMD.head= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}head
${_TOOLS_VARNAME.head}= ${TOOLS_REAL_CMD.head}
. endif
.endif
.if !defined(TOOLS_IGNORE.hostname) && !empty(_USE_TOOLS:Mhostname)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.hostname=
. elif !empty(_TOOLS_USE_PKGSRC.hostname:M[yY][eE][sS])
TOOLS_DEPENDS.hostname?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= hostname
TOOLS_REAL_CMD.hostname= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}hostname
${_TOOLS_VARNAME.hostname}= ${TOOLS_REAL_CMD.hostname}
. endif
.endif
.if !defined(TOOLS_IGNORE.id) && !empty(_USE_TOOLS:Mid)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.id=
. elif !empty(_TOOLS_USE_PKGSRC.id:M[yY][eE][sS])
TOOLS_DEPENDS.id?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= id
TOOLS_REAL_CMD.id= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}id
${_TOOLS_VARNAME.id}= ${TOOLS_REAL_CMD.id}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.lex) && !empty(_USE_TOOLS:Mlex)
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
. if !empty(PKGPATH:Mdevel/flex)
MAKEFLAGS+= TOOLS_IGNORE.lex=
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
. elif !empty(_TOOLS_USE_PKGSRC.lex:M[yY][eE][sS])
. include "../../devel/flex/buildlink3.mk"
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.lex?= ${BUILDLINK_DEPENDS.flex}:${BUILDLINK_PKGSRCDIR.flex}
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
TOOLS_SYMLINK+= lex
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
TOOLS_REAL_CMD.lex= ${LOCALBASE}/bin/flex
${_TOOLS_VARNAME.lex}= ${TOOLS_REAL_CMD.lex}
. endif
.endif
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.ln) && !empty(_USE_TOOLS:Mln)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.ln=
. elif !empty(_TOOLS_USE_PKGSRC.ln:M[yY][eE][sS])
TOOLS_DEPENDS.ln?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= ln
TOOLS_REAL_CMD.ln= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}ln
${_TOOLS_VARNAME.ln}= ${TOOLS_REAL_CMD.ln}
. endif
.endif
.if !defined(TOOLS_IGNORE.ls) && !empty(_USE_TOOLS:Mls)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.ls=
. elif !empty(_TOOLS_USE_PKGSRC.ls:M[yY][eE][sS])
TOOLS_DEPENDS.ls?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= ls
TOOLS_REAL_CMD.ls= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}ls
${_TOOLS_VARNAME.ls}= ${TOOLS_REAL_CMD.ls}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.m4) && !empty(_USE_TOOLS:Mm4)
Teach replace.mk about awk, m4, and sed when the GNU versions aren't required.
2005-04-27 18:28:19 +02:00
. if !empty(PKGPATH:Mdevel/m4)
MAKEFLAGS+= TOOLS_IGNORE.m4=
. elif !empty(_TOOLS_USE_PKGSRC.m4:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.m4?= m4>=1.4:../../devel/m4
Teach replace.mk about awk, m4, and sed when the GNU versions aren't required.
2005-04-27 18:28:19 +02:00
TOOLS_SYMLINK+= m4
TOOLS_REAL_CMD.m4= ${LOCALBASE}/bin/gm4
${_TOOLS_VARNAME.m4}= ${TOOLS_REAL_CMD.m4}
. endif
.endif
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.mkdir) && !empty(_USE_TOOLS:Mmkdir)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.mkdir=
. elif !empty(_TOOLS_USE_PKGSRC.mkdir:M[yY][eE][sS])
TOOLS_DEPENDS.mkdir?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_WRAP+= mkdir
TOOLS_REAL_CMD.mkdir= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}mkdir
TOOLS_ARGS.mkdir= -p
${_TOOLS_VARNAME.mkdir}= ${TOOLS_REAL_CMD.mkdir} ${TOOLS_ARGS.mkdir}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.mtree) && !empty(_USE_TOOLS:Mmtree)
Teach replace about mtree/MTREE.
2005-04-27 08:15:53 +02:00
. if !empty(PKGPATH:Mpkgtools/mtree)
MAKEFLAGS+= TOOLS_IGNORE.mtree=
. elif !empty(_TOOLS_USE_PKGSRC.mtree:M[yY][eE][sS])
We can't add dependencies on packages that are never registered. archivers/pax and pkgtools/mtree fall in this category since they are usually installed by pkgsrc bootstrap.
2005-04-27 17:21:50 +02:00
#
# This is installed by pkgsrc bootstrap, and is never registered, so
# comment out the dependency on it.
#
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
#TOOLS_DEPENDS.mtree?= mtree>=20040722:../../pkgtools/mtree
Teach replace about mtree/MTREE.
2005-04-27 08:15:53 +02:00
TOOLS_SYMLINK+= mtree
TOOLS_REAL_CMD.mtree= ${LOCALBASE}/bin/mtree
${_TOOLS_VARNAME.mtree}= ${TOOLS_REAL_CMD.mtree}
. endif
.endif
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.mv) && !empty(_USE_TOOLS:Mmv)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.mv=
. elif !empty(_TOOLS_USE_PKGSRC.mv:M[yY][eE][sS])
TOOLS_DEPENDS.mv?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= mv
TOOLS_REAL_CMD.mv= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}mv
${_TOOLS_VARNAME.mv}= ${TOOLS_REAL_CMD.mv}
. endif
.endif
.if !defined(TOOLS_IGNORE.nice) && !empty(_USE_TOOLS:Mnice)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.nice=
. elif !empty(_TOOLS_USE_PKGSRC.nice:M[yY][eE][sS])
TOOLS_DEPENDS.nice?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= nice
TOOLS_REAL_CMD.nice= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}nice
${_TOOLS_VARNAME.nice}= ${TOOLS_REAL_CMD.nice}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.patch) && !empty(_USE_TOOLS:Mpatch)
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
. if !empty(PKGPATH:Mdevel/patch)
MAKEFLAGS+= TOOLS_IGNORE.patch=
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
. elif !empty(_TOOLS_USE_PKGSRC.patch:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.patch?= patch>=2.2:../../devel/patch
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
TOOLS_SYMLINK+= patch
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
TOOLS_REAL_CMD.patch= ${LOCALBASE}/bin/gpatch
${_TOOLS_VARNAME.patch}= ${TOOLS_REAL_CMD.patch}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.pax) && !empty(_USE_TOOLS:Mpax)
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
. if !empty(PKGPATH:Marchivers/pax)
MAKEFLAGS+= TOOLS_IGNORE.pax=
. elif !empty(_TOOLS_USE_PKGSRC.pax:M[yY][eE][sS])
#
# This is installed by pkgsrc bootstrap, and is never registered, so
# comment out the dependency on it.
#
#TOOLS_DEPENDS.pax?= pax>=20040802:../../archivers/pax
TOOLS_SYMLINK+= pax
TOOLS_REAL_CMD.pax= ${LOCALBASE}/bin/pax
${_TOOLS_VARNAME.pax}= ${TOOLS_REAL_CMD.pax}
. endif
.endif
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.pwd) && !empty(_USE_TOOLS:Mpwd)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.pwd=
. elif !empty(_TOOLS_USE_PKGSRC.pwd:M[yY][eE][sS])
TOOLS_DEPENDS.pwd?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= pwd
TOOLS_REAL_CMD.pwd= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}pwd
${_TOOLS_VARNAME.pwd}= ${TOOLS_REAL_CMD.pwd}
. endif
.endif
.if !defined(TOOLS_IGNORE.rm) && !empty(_USE_TOOLS:Mrm)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.rm=
. elif !empty(_TOOLS_USE_PKGSRC.rm:M[yY][eE][sS])
TOOLS_DEPENDS.rm?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= rm
TOOLS_REAL_CMD.rm= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}rm
${_TOOLS_VARNAME.rm}= ${TOOLS_REAL_CMD.rm}
. endif
.endif
.if !defined(TOOLS_IGNORE.rmdir) && !empty(_USE_TOOLS:Mrmdir)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.rmdir=
. elif !empty(_TOOLS_USE_PKGSRC.rmdir:M[yY][eE][sS])
TOOLS_DEPENDS.rmdir?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= rmdir
TOOLS_REAL_CMD.rmdir= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}rmdir
${_TOOLS_VARNAME.rmdir}= ${TOOLS_REAL_CMD.rmdir}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.sed) && !empty(_USE_TOOLS:Msed)
Teach replace.mk about awk, m4, and sed when the GNU versions aren't required.
2005-04-27 18:28:19 +02:00
. if !empty(PKGPATH:Mtextproc/nbsed)
MAKEFLAGS+= TOOLS_IGNORE.sed=
. elif !empty(_TOOLS_USE_PKGSRC.sed:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.sed?= nbsed>=20040821:../../textproc/nbsed
Teach replace.mk about awk, m4, and sed when the GNU versions aren't required.
2005-04-27 18:28:19 +02:00
TOOLS_SYMLINK+= sed
TOOLS_REAL_CMD.sed= ${LOCALBASE}/bin/nbsed
${_TOOLS_VARNAME.sed}= ${TOOLS_REAL_CMD.sed}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.sh) && !empty(_USE_TOOLS:Msh)
Teach replace.mk about replacements for SH (shells/pdksh) and SHLOCK (pkgtools/shlock).
2005-04-27 06:47:41 +02:00
. if !empty(PKGPATH:Mshells/pdksh)
MAKEFLAGS+= TOOLS_IGNORE.sh=
. elif !empty(_TOOLS_USE_PKGSRC.sh:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.sh?= pdksh>=5.2.14:../../shells/pdksh
Teach replace.mk about replacements for SH (shells/pdksh) and SHLOCK (pkgtools/shlock).
2005-04-27 06:47:41 +02:00
TOOLS_SYMLINK+= sh
TOOLS_REAL_CMD.sh= ${LOCALBASE}/bin/pdksh
${_TOOLS_VARNAME.sh}= ${TOOLS_REAL_CMD.sh}
. endif
TOOLS_CMD.sh= ${TOOLS_DIR}/bin/sh
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.shlock) && !empty(_USE_TOOLS:Mshlock)
Teach replace.mk about replacements for SH (shells/pdksh) and SHLOCK (pkgtools/shlock).
2005-04-27 06:47:41 +02:00
. if !empty(PKGPATH:Mpkgtools/shlock)
MAKEFLAGS+= TOOLS_IGNORE.shlock=
. elif !empty(_TOOLS_USE_PKGSRC.shlock:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.shlock?= shlock>=20020114:../../pkgtools/shlock
Teach replace.mk about replacements for SH (shells/pdksh) and SHLOCK (pkgtools/shlock).
2005-04-27 06:47:41 +02:00
TOOLS_SYMLINK+= shlock
TOOLS_REAL_CMD.shlock= ${LOCALBASE}/bin/shlock
${_TOOLS_VARNAME.shlock}= ${TOOLS_REAL_CMD.shlock}
. endif
.endif
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.sort) && !empty(_USE_TOOLS:Msort)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.sort=
. elif !empty(_TOOLS_USE_PKGSRC.sort:M[yY][eE][sS])
TOOLS_DEPENDS.sort?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= sort
TOOLS_REAL_CMD.sort= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}sort
${_TOOLS_VARNAME.sort}= ${TOOLS_REAL_CMD.sort}
. endif
.endif
.if !defined(TOOLS_IGNORE.tail) && !empty(_USE_TOOLS:Mtail)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.tail=
. elif !empty(_TOOLS_USE_PKGSRC.tail:M[yY][eE][sS])
TOOLS_DEPENDS.tail?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= tail
TOOLS_REAL_CMD.tail= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}tail
${_TOOLS_VARNAME.tail}= ${TOOLS_REAL_CMD.tail}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.tbl) && !empty(_USE_TOOLS:Mtbl)
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
. if !empty(PKGPATH:Mtextproc/groff)
MAKEFLAGS+= TOOLS_IGNORE.tbl=
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
. elif !empty(_TOOLS_USE_PKGSRC.tbl:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.tbl?= groff>=1.19nb4:../../textproc/groff
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
TOOLS_SYMLINK+= tbl
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
TOOLS_REAL_CMD.tbl= ${LOCALBASE}/bin/tbl
${_TOOLS_VARNAME.tbl}= ${TOOLS_REAL_CMD.tbl}
. endif
.endif
Merge coreutils.mk into replace.mk. Also remove the "coreutils" option to USE_TOOLS and replace it with the names of the various tools we're getting from coreutils, e.g. "mv", "mkdir", "rm", etc.
2005-04-28 19:35:48 +02:00
.if !defined(TOOLS_IGNORE.tee) && !empty(_USE_TOOLS:Mtee)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.tee=
. elif !empty(_TOOLS_USE_PKGSRC.tee:M[yY][eE][sS])
TOOLS_DEPENDS.tee?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= tee
TOOLS_REAL_CMD.tee= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}tee
${_TOOLS_VARNAME.tee}= ${TOOLS_REAL_CMD.tee}
. endif
.endif
.if !defined(TOOLS_IGNORE.test) && !empty(_USE_TOOLS:Mtest)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.test=
. elif !empty(_TOOLS_USE_PKGSRC.test:M[yY][eE][sS])
TOOLS_DEPENDS.test?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= test
TOOLS_REAL_CMD.test= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}test
${_TOOLS_VARNAME.test}= ${TOOLS_REAL_CMD.test}
. endif
.endif
.if !defined(TOOLS_IGNORE.touch) && !empty(_USE_TOOLS:Mtouch)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.touch=
. elif !empty(_TOOLS_USE_PKGSRC.touch:M[yY][eE][sS])
TOOLS_DEPENDS.touch?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= touch
TOOLS_REAL_CMD.touch= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}touch
${_TOOLS_VARNAME.touch}= ${TOOLS_REAL_CMD.touch}
. endif
.endif
.if !defined(TOOLS_IGNORE.tr) && !empty(_USE_TOOLS:Mtr)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.tr=
. elif !empty(_TOOLS_USE_PKGSRC.tr:M[yY][eE][sS])
TOOLS_DEPENDS.tr?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= tr
TOOLS_REAL_CMD.tr= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}tr
${_TOOLS_VARNAME.tr}= ${TOOLS_REAL_CMD.tr}
. endif
.endif
.if !defined(TOOLS_IGNORE.true) && !empty(_USE_TOOLS:Mtrue)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.true=
. elif !empty(_TOOLS_USE_PKGSRC.true:M[yY][eE][sS])
TOOLS_DEPENDS.true?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= true
TOOLS_REAL_CMD.true= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}true
${_TOOLS_VARNAME.true}= ${TOOLS_REAL_CMD.true}
. endif
.endif
.if !defined(TOOLS_IGNORE.tsort) && !empty(_USE_TOOLS:Mtsort)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.tsort=
. elif !empty(_TOOLS_USE_PKGSRC.tsort:M[yY][eE][sS])
TOOLS_DEPENDS.tsort?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= tsort
TOOLS_REAL_CMD.tsort= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}tsort
${_TOOLS_VARNAME.tsort}= ${TOOLS_REAL_CMD.tsort}
. endif
.endif
.if !defined(TOOLS_IGNORE.wc) && !empty(_USE_TOOLS:Mwc)
. if !empty(PKGPATH:Msysutils/coreutils)
MAKEFLAGS+= TOOLS_IGNORE.wc=
. elif !empty(_TOOLS_USE_PKGSRC.wc:M[yY][eE][sS])
TOOLS_DEPENDS.wc?= coreutils>=5.2.1:../../sysutils/coreutils
TOOLS_SYMLINK+= wc
TOOLS_REAL_CMD.wc= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}wc
${_TOOLS_VARNAME.wc}= ${TOOLS_REAL_CMD.wc}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.xargs) && !empty(_USE_TOOLS:Mxargs)
Split out the tools from the same package into separate clauses so that you can specify wanting individual tools from that package.
2005-04-28 05:57:39 +02:00
. if !empty(PKGPATH:Msysutils/findutils)
MAKEFLAGS+= TOOLS_IGNORE.xargs=
. elif !empty(_TOOLS_USE_PKGSRC.xargs:M[yY][eE][sS])
TOOLS_DEPENDS.xargs?= findutils>=4.1:../../sysutils/findutils
TOOLS_SYMLINK+= xargs
TOOLS_REAL_CMD.xargs= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}xargs
${_TOOLS_VARNAME.xargs}= ${TOOLS_REAL_CMD.xargs}
. endif
.endif
Create _USE_TOOLS, a sanitized versino of USE_TOOLS that removes the tools that are overridden by superseding ones. Use it in place of USE_TOOLS in most places. This fixes the situation where we can depend on the tool that overridden, e.g. USE_TOOLS= gawk awk.
2005-04-28 17:47:43 +02:00
.if !defined(TOOLS_IGNORE.yacc) && !empty(_USE_TOOLS:Myacc)
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
. if !empty(PKGPATH:Mdevel/bison)
MAKEFLAGS+= TOOLS_IGNORE.yacc=
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
. elif !empty(_TOOLS_USE_PKGSRC.yacc:M[yY][eE][sS])
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.yacc?= bison>=1.0:../../devel/bison
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
TOOLS_WRAP+= yacc
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
TOOLS_REAL_CMD.yacc= ${LOCALBASE}/bin/bison
TOOLS_ARGS.yacc= -y
${_TOOLS_VARNAME.yacc}= ${TOOLS_REAL_CMD.yacc} ${TOOLS_ARGS.yacc}
. endif
.endif
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
# Add the dependencies for each pkgsrc-supplied tool.
We only need to loop over the tools that we say we're going to use.
2005-04-28 17:51:10 +02:00
.for _t_ in ${_USE_TOOLS}
. if defined(TOOLS_DEPMETHOD.${_t_}) && defined(TOOLS_DEPENDS.${_t_})
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
. if empty(${TOOLS_DEPMETHOD.${_t_}}:M${TOOLS_DEPENDS.${_t_}})
${TOOLS_DEPMETHOD.${_t_}}+= ${TOOLS_DEPENDS.${_t_}}
. endif
. endif
.endfor
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
######################################################################
# Set TOOLS_REAL_CMD.<tool> appropriately in the case where we are
PLATFORM_TOOL.<tool> is meant to be set like the "TOOL" variable, so also create either a wrapper or a symlink depending on whether it has any arguments or not. While we're here, correct the comment block to include a description of PLATFORM_TOOL.*.
2005-04-26 18:19:37 +02:00
# using the system-supplied tool. Here, we first check to see if
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_PLATFORM.<tool> is defined. If it is, then use that as the
# path to the real command and extract any arguments into
# TOOLS_ARGS.<tool>. We also create either a wrapper or a symlink
# depending on whether # there are any arguments or not. Lastly,
PLATFORM_TOOL.<tool> is meant to be set like the "TOOL" variable, so also create either a wrapper or a symlink depending on whether it has any arguments or not. While we're here, correct the comment block to include a description of PLATFORM_TOOL.*.
2005-04-26 18:19:37 +02:00
# always set the TOOL name for each tool to point to the real command,
Only set the "TOOL" variable if it was associated with the corresponding <tool>.
2005-04-26 20:59:48 +02:00
# e.g., TBL, YACC, etc., provided that "TOOL" has been associated with
# <tool>.
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
#
We only need to loop over the tools that we say we're going to use.
2005-04-28 17:51:10 +02:00
.for _t_ in ${_USE_TOOLS}
. if !defined(TOOLS_IGNORE.${_t_}) && \
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
!empty(_TOOLS_USE_PKGSRC.${_t_}:M[nN][oO])
Rename PLATFORM_TOOLS.* to TOOLS_PLATFORM.* to bring the variable names under the same namespace as the other parts of the new tools framework.
2005-04-27 18:52:28 +02:00
. if defined(TOOLS_PLATFORM.${_t_}) && !empty(TOOLS_PLATFORM.${_t_})
If PLATFORM_TOOL.<tool> is defined for a particular tool, then use it instead of the pkgsrc version of the tool. This is an alternative to adding the appropriate platform to the _TOOLS_USE_PLATFORM.* tables.
2005-04-25 08:16:38 +02:00
TOOLS_REAL_CMD.${_t_}?= \
Rename PLATFORM_TOOLS.* to TOOLS_PLATFORM.* to bring the variable names under the same namespace as the other parts of the new tools framework.
2005-04-27 18:52:28 +02:00
${TOOLS_PLATFORM.${_t_}:C/^/_asdf_/1:M_asdf_*:S/^_asdf_//}
If PLATFORM_TOOL.<tool> is defined for a particular tool, then use it instead of the pkgsrc version of the tool. This is an alternative to adding the appropriate platform to the _TOOLS_USE_PLATFORM.* tables.
2005-04-25 08:16:38 +02:00
TOOLS_ARGS.${_t_}?= \
Rename PLATFORM_TOOLS.* to TOOLS_PLATFORM.* to bring the variable names under the same namespace as the other parts of the new tools framework.
2005-04-27 18:52:28 +02:00
${TOOLS_PLATFORM.${_t_}:C/^/_asdf_/1:N_asdf_*}
Only set the "TOOL" variable if one has been associated with the tool.
2005-04-28 19:40:52 +02:00
. if defined(_TOOLS_VARNAME.${_t_})
Rename PLATFORM_TOOLS.* to TOOLS_PLATFORM.* to bring the variable names under the same namespace as the other parts of the new tools framework.
2005-04-27 18:52:28 +02:00
${_TOOLS_VARNAME.${_t_}}= ${TOOLS_PLATFORM.${_t_}}
Only set the "TOOL" variable if one has been associated with the tool.
2005-04-28 19:40:52 +02:00
. endif
PLATFORM_TOOL.<tool> is meant to be set like the "TOOL" variable, so also create either a wrapper or a symlink depending on whether it has any arguments or not. While we're here, correct the comment block to include a description of PLATFORM_TOOL.*.
2005-04-26 18:19:37 +02:00
. if !empty(TOOLS_ARGS.${_t_})
TOOLS_WRAP+= ${_t_}
. else
TOOLS_SYMLINK+= ${_t_}
. endif
Only set the "TOOL" variable if it was associated with the corresponding <tool>.
2005-04-26 20:59:48 +02:00
. elif defined(_TOOLS_VARNAME.${_t_})
. if defined(TOOLS_REAL_CMD.${_t_})
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
${_TOOLS_VARNAME.${_t_}}= ${TOOLS_REAL_CMD.${_t_}} ${TOOLS_ARGS.${_t_}}
Only set the "TOOL" variable if it was associated with the corresponding <tool>.
2005-04-26 20:59:48 +02:00
. else
Rewrite code for using system-supplied tools so that we can replace tools that are defined as a command plus arguments, e.g. for gunzip, GUNZIP= /usr/bin/gzip -d In this case, we generate a wrapper script that invokes the real command plus arguments. If there are no arguments, then just symlink the command for simplicity. Also, restructure the tool-specific blocks so that we always define TOOLS_CMD.<tool> to the correct name (important for yacc/bison), and check that the real command actually exists before assigning it to the "TOOL" name.
2005-04-24 05:07:36 +02:00
${_TOOLS_VARNAME.${_t_}}= ${_TOOLS_VARNAME.${_t_}}_not_defined_
Only set the "TOOL" variable if it was associated with the corresponding <tool>.
2005-04-26 20:59:48 +02:00
. endif
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
. endif
. endif
.endfor
.undef _t_
Reference in a new issue Copy permalink