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

569 lines
19 KiB
Makefile
Raw Normal View History

Initial stab at creating lists of system-supplied tools for each platform. These were culled from pkgsrc/mk/${OPSYS}.mk. These files should only be listing utilities that aren't installed by pkgsrc.
2005-04-27 17:28:16 +02:00
# $NetBSD: replace.mk,v 1.36 2005/04/27 15:28:16 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,
# but this may be changed by explicitly setting TOOLS_DEPENDS.<tool>,
# e.g.:
#
# TOOLS_DEPENDS.tbl= DEPENDS
#
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
.if defined(USE_PERL5)
USE_TOOLS+= perl
.endif
Initial stab at creating lists of system-supplied tools for each platform. These were culled from pkgsrc/mk/${OPSYS}.mk. These files should only be listing utilities that aren't installed by pkgsrc.
2005-04-27 17:28:16 +02:00
# These are the platform-specific lists of system-supplied tools.
#
# XXX These should eventually just migrate over to the appropriate
# XXX pkgsrc/mk/platform/${OPSYS}.mk file.
#
.if exists(../../mk/tools/tools.${OPSYS}.mk)
. include "../../mk/tools/tools.${OPSYS}.mk"
.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
# Only allow one of "bison" and "yacc".
.if !empty(USE_TOOLS:Mbison) && !empty(USE_TOOLS:Myacc)
PKG_FAIL_REASON+= "\`\`bison'' and \`\`yacc'' conflict in USE_TOOLS."
.endif
# This is an exhaustive list of tools for which we have pkgsrc
# replacements.
#
Teach replace.mk about cmp/CMP.
2005-04-27 01:20:35 +02:00
_TOOLS_REPLACE_LIST= bison cmp egrep fgrep file find gawk gm4 gmake \
Teach replace about mtree/MTREE.
2005-04-27 08:15:53 +02:00
grep gsed gtar gunzip gzcat gzip lex mtree \
patch pax perl sh shlock tbl xargs 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
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
# "TOOL" variable names associated with each of the tools
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_VARNAME.bison= YACC
Teach replace.mk about cmp/CMP.
2005-04-27 01:20:35 +02:00
_TOOLS_VARNAME.cmp= CMP
Teach replace.mk about egrep, fgrep, and file.
2005-04-15 18:01:23 +02:00
_TOOLS_VARNAME.egrep= EGREP
_TOOLS_VARNAME.fgrep= FGREP
_TOOLS_VARNAME.file= FILE_CMD
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
_TOOLS_VARNAME.find= FIND
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_VARNAME.gawk= AWK
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_VARNAME.gm4= M4
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_VARNAME.gmake= GMAKE
_TOOLS_VARNAME.grep= GREP
Rename the "sed" option for USE_TOOLS to "gsed" to note that we want GNU sed.
2005-04-26 21:11:25 +02:00
_TOOLS_VARNAME.gsed= SED
Teach replace.mk about GTAR and PAX (replace with archivers/pax if necessary).
2005-04-27 05:41:17 +02:00
_TOOLS_VARNAME.gtar= GTAR
Teach replace.mk about gzip, gunzip, and gzcat.
2005-04-24 05:59:44 +02:00
_TOOLS_VARNAME.gunzip= GUNZIP_CMD
_TOOLS_VARNAME.gzcat= GZCAT
_TOOLS_VARNAME.gzip= GZIP_CMD
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_VARNAME.lex= LEX
Teach replace about mtree/MTREE.
2005-04-27 08:15:53 +02:00
_TOOLS_VARNAME.mtree= MTREE
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_VARNAME.patch= PATCH
Teach replace.mk about GTAR and PAX (replace with archivers/pax if necessary).
2005-04-27 05:41:17 +02:00
_TOOLS_VARNAME.pax= PAX
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_VARNAME.perl= PERL5
Teach replace.mk about replacements for SH (shells/pdksh) and SHLOCK (pkgtools/shlock).
2005-04-27 06:47:41 +02:00
_TOOLS_VARNAME.sh= SH
_TOOLS_VARNAME.shlock= SHLOCK
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_VARNAME.tbl= TBL
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
_TOOLS_VARNAME.xargs= XARGS
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_VARNAME.yacc= YACC
######################################################################
# For each tool, _TOOLS_USE_PLATFORM.<tool> is a list of platforms for
# which we will use the system-supplied tool instead of the pkgsrc
# version.
#
# This table should probably be split amongst the various mk/platform
# files as they are ${OPSYS}-specific.
#
_TOOLS_USE_PLATFORM.bison= Linux-*-*
Teach replace.mk about cmp/CMP.
2005-04-27 01:20:35 +02:00
_TOOLS_USE_PLATFORM.cmp= BSDOS-*-* Darwin-*-* DragonFly-*-* \
FreeBSD-*-* IRIX-*-* Interix-*-* \
Linux-*-* NetBSD-*-* OSF1-*-* \
OpenBSD-*-* SunOS-*-*
Platforms that have GNU grep also have egrep and fgrep.
2005-04-25 01:28:20 +02:00
_TOOLS_USE_PLATFORM.egrep= ${_TOOLS_USE_PLATFORM.grep}
_TOOLS_USE_PLATFORM.fgrep= ${_TOOLS_USE_PLATFORM.grep}
Alphabetize the platform tools lists.
2005-04-25 01:32:09 +02:00
_TOOLS_USE_PLATFORM.file= Darwin-*-* DragonFly-*-* FreeBSD-*-* \
Linux-*-* NetBSD-*-* OpenBSD-*-* \
SunOS-*-*
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
_TOOLS_USE_PLATFORM.find= Linux-*-*
Alphabetize the platform tools lists.
2005-04-25 01:32:09 +02:00
_TOOLS_USE_PLATFORM.gawk= DragonFly-*-* FreeBSD-*-* Interix-*-* \
Linux-*-* NetBSD-1.[0-6]*-* OpenBSD-*-* \
Teach replace.mk about egrep, fgrep, and file.
2005-04-15 18:01:23 +02:00
SunOS-*-*
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_USE_PLATFORM.gm4= # empty
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_PLATFORM.gmake= Darwin-*-*
Alphabetize the platform tools lists.
2005-04-25 01:32:09 +02:00
_TOOLS_USE_PLATFORM.grep= Darwin-*-* DragonFly-*-* FreeBSD-*-* \
Linux-*-* NetBSD-*-* OpenBSD-*-* \
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
SunOS-*-*
Rename the "sed" option for USE_TOOLS to "gsed" to note that we want GNU sed.
2005-04-26 21:11:25 +02:00
_TOOLS_USE_PLATFORM.gsed= Interix-*-* Linux-*-* SunOS-*-*
Teach replace.mk about GTAR and PAX (replace with archivers/pax if necessary).
2005-04-27 05:41:17 +02:00
_TOOLS_USE_PLATFORM.gtar= ${_TOOLS_USE_PLATFORM.pax}
Teach replace.mk about gzip, gunzip, and gzcat.
2005-04-24 05:59:44 +02:00
_TOOLS_USE_PLATFORM.gunzip= ${_TOOLS_USE_PLATFORM.gzip}
_TOOLS_USE_PLATFORM.gzcat= ${_TOOLS_USE_PLATFORM.gzip}
_TOOLS_USE_PLATFORM.gzip= BSDOS-*-* Darwin-*-* DragonFly-*-* \
FreeBSD-*-* IRIX-*-* Interix-*-* \
Linux-*-* NetBSD-*-* OSF1-*-* \
OpenBSD-*-* SunOS-*-*
Alphabetize the platform tools lists.
2005-04-25 01:32:09 +02:00
_TOOLS_USE_PLATFORM.lex= DragonFly-*-* FreeBSD-*-* Linux-*-* \
NetBSD-*-* OpenBSD-*-*
Teach replace about mtree/MTREE.
2005-04-27 08:15:53 +02:00
_TOOLS_USE_PLATFORM.mtree= BSDOS-*-* Darwin-*-* DragonFly-*-* \
FreeBSD-*-* NetBSD-*-* OpenBSD-*-*
Alphabetize the platform tools lists.
2005-04-25 01:32:09 +02:00
_TOOLS_USE_PLATFORM.patch= Darwin-*-* DragonFly-*-* FreeBSD-*-* \
Linux-*-* NetBSD-*-* OpenBSD-*-* \
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
SunOS-*-*
Teach replace.mk about GTAR and PAX (replace with archivers/pax if necessary).
2005-04-27 05:41:17 +02:00
_TOOLS_USE_PLATFORM.pax= Darwin-*-* DragonFly-*-* FreeBSD-*-* \
Interix-*-* Linux-*-* NetBSD-*-* \
OpenBSD-*-*
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_PLATFORM.perl= # This should always be empty.
Teach replace.mk about replacements for SH (shells/pdksh) and SHLOCK (pkgtools/shlock).
2005-04-27 06:47:41 +02:00
_TOOLS_USE_PLATFORM.sh= *-*-* # every platform has a Bourne shell
_TOOLS_USE_PLATFORM.shlock= AIX-*-* Darwin-*-* DragonFly-*-* \
FreeBSD-*-* NetBSD-*-*
Alphabetize the platform tools lists.
2005-04-25 01:32:09 +02:00
_TOOLS_USE_PLATFORM.tbl= DragonFly-*-* FreeBSD-*-* NetBSD-*-* \
OpenBSD-*-*
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
_TOOLS_USE_PLATFORM.xargs= ${_TOOLS_USE_PLATFORM.find}
Alphabetize the platform tools lists.
2005-04-25 01:32:09 +02:00
_TOOLS_USE_PLATFORM.yacc= DragonFly-*-* FreeBSD-*-* NetBSD-*-* \
OpenBSD-*-*
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 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
# use the system-supplied one if PLATFORM_TOOL.<tool> is non-empty, or
# 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
#
.for _t_ in ${_TOOLS_REPLACE_LIST}
. for _pattern_ in ${_TOOLS_USE_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
. if defined(PLATFORM_TOOL.${_t_}) && !empty(PLATFORM_TOOL.${_t_})
_TOOLS_USE_PKGSRC.${_t_}?= no
. 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 !empty(MACHINE_PLATFORM:M${_pattern_})
_TOOLS_USE_PKGSRC.${_t_}?= no
. endif
. endfor
. undef _pattern_
_TOOLS_USE_PKGSRC.${_t_}?= yes
.endfor
.undef _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_DEPENDS.<tool> defaults to 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
.for _t_ in ${_TOOLS_REPLACE_LIST}
TOOLS_DEPENDS.${_t_}?= BUILD_DEPENDS
.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.
#
.if !defined(TOOLS_IGNORE.bison) && !empty(USE_TOOLS:Mbison)
. 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])
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
${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
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
. if exists(${TOOLS_REAL_CMD.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_VARNAME.bison}= ${TOOLS_REAL_CMD.bison} ${TOOLS_ARGS.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
. 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
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 replace.mk about cmp/CMP.
2005-04-27 01:20:35 +02:00
.if !defined(TOOLS_IGNORE.cmp) && !empty(USE_TOOLS:Mcmp)
. if !empty(PKGPATH:Mdevel/diffutils)
MAKEFLAGS+= TOOLS_IGNORE.cmp=
. elif !empty(_TOOLS_USE_PKGSRC.cmp:M[yY][eE][sS])
${TOOLS_DEPENDS.cmp}+= diffutils>=2.8.1:../../devel/diffutils
TOOLS_WRAP+= cmp
TOOLS_REAL_CMD.cmp= ${LOCALBASE}/bin/cmp
. if exists(${TOOLS_REAL_CMD.cmp})
${_TOOLS_VARNAME.cmp}= ${TOOLS_REAL_CMD.cmp}
. endif
. endif
.endif
Fix conditions on grep and gzip so that if any of the TOOLS_IGNORE.* are defined for their respective utilities, then we skip the processing to avoid dependency loops.
2005-04-26 23:56:13 +02:00
.if (!defined(TOOLS_IGNORE.egrep) && \
!defined(TOOLS_IGNORE.fgrep) && \
!defined(TOOLS_IGNORE.grep)) && \
(!empty(USE_TOOLS:Megrep) || \
!empty(USE_TOOLS:Mfgrep) || \
!empty(USE_TOOLS:Mgrep))
Make some code more cut-n-paste-friendly for packages that replace lots of tools.
2005-04-27 00:10:53 +02:00
_TOOLS_GREPUTILS= egrep fgrep grep
Sort the tool-specific sections for easier browsing.
2005-04-26 21:15:38 +02:00
. if !empty(PKGPATH:Mtextproc/grep)
Make some code more cut-n-paste-friendly for packages that replace lots of tools.
2005-04-27 00:10:53 +02:00
. for _t_ in ${_TOOLS_GREPUTILS}
MAKEFLAGS+= TOOLS_IGNORE.${_t_}=
. endfor
Sort the tool-specific sections for easier browsing.
2005-04-26 21:15:38 +02:00
. else
Make some code more cut-n-paste-friendly for packages that replace lots of tools.
2005-04-27 00:10:53 +02:00
. for _t_ in ${_TOOLS_GREPUTILS}
Sort the tool-specific sections for easier browsing.
2005-04-26 21:15:38 +02:00
. if empty(USE_TOOLS:M${_t_})
USE_TOOLS+= ${_t_}
. endif
. endfor
. if !empty(_TOOLS_USE_PKGSRC.egrep:M[yY][eE][sS]) || \
!empty(_TOOLS_USE_PKGSRC.fgrep:M[yY][eE][sS]) || \
!empty(_TOOLS_USE_PKGSRC.grep:M[yY][eE][sS])
${TOOLS_DEPENDS.grep}+= grep>=2.5.1:../../textproc/grep
Continue the work in previous commit by making the code more cut-n-paste-friendly for packages with large numbers of utilities.
2005-04-27 00:18:14 +02:00
. for _t_ in ${_TOOLS_GREPUTILS}
If we're using one of the package's utilities, we're going to be using them all, so make sure _TOOLS_USE_PKGSRC.* is set to "yes".
2005-04-27 00:20:42 +02:00
_TOOLS_USE_PKGSRC.${_t_}= yes
Continue the work in previous commit by making the code more cut-n-paste-friendly for packages with large numbers of utilities.
2005-04-27 00:18:14 +02:00
TOOLS_SYMLINK+= ${_t_}
TOOLS_REAL_CMD.${_t_}= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}${_t_}
To avoid errors, check that there is a TOOL variable associated with the tool before we set it.
2005-04-27 00:51:00 +02:00
. if defined(_TOOLS_VARNAME.${_t_}) && exists(${TOOLS_REAL_CMD.${_t_}})
Continue the work in previous commit by making the code more cut-n-paste-friendly for packages with large numbers of utilities.
2005-04-27 00:18:14 +02:00
${_TOOLS_VARNAME.${_t_}}= ${TOOLS_REAL_CMD.${_t_}}
. endif
. endfor
Sort the tool-specific sections for easier browsing.
2005-04-26 21:15:38 +02:00
. endif
. endif
.endif
Teach replace.mk about egrep, fgrep, and file.
2005-04-15 18:01:23 +02:00
.if !defined(TOOLS_IGNORE.file) && !empty(USE_TOOLS:Mfile)
. 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])
Teach replace.mk about egrep, fgrep, and file.
2005-04-15 18:01:23 +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
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
. if exists(${TOOLS_REAL_CMD.file})
Teach replace.mk about egrep, fgrep, and file.
2005-04-15 18:01:23 +02:00
${_TOOLS_VARNAME.file}= ${TOOLS_REAL_CMD.file}
. endif
. endif
.endif
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 (!defined(TOOLS_IGNORE.find) && \
!defined(TOOLS_IGNORE.xargs)) && \
(!empty(USE_TOOLS:Mfind) || \
!empty(USE_TOOLS:Mxargs))
_TOOLS_FINDUTILS= find xargs
. if !empty(PKGPATH:Msysutils/findutils)
. for _t_ in ${_TOOLS_FINDUTILS}
MAKEFLAGS+= TOOLS_IGNORE.${_t_}=
. endfor
. else
. for _t_ in ${_TOOLS_FINDUTILS}
. if empty(USE_TOOLS:M${_t_})
USE_TOOLS+= ${_t_}
. endif
. endfor
. if !empty(_TOOLS_USE_PKGSRC.find:M[yY][eE][sS]) || \
!empty(_TOOLS_USE_PKGSRC.xargs:M[yY][eE][sS])
${TOOLS_DEPENDS.find}+= findutils>=4.1:../../sysutils/findutils
. for _t_ in ${_TOOLS_FINDUTILS}
_TOOLS_USE_PKGSRC.${_t_}= yes
TOOLS_SYMLINK+= ${_t_}
TOOLS_REAL_CMD.${_t_}= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}${_t_}
To avoid errors, check that there is a TOOL variable associated with the tool before we set it.
2005-04-27 00:51:00 +02:00
. if defined(_TOOLS_VARNAME.${_t_}) && exists(${TOOLS_REAL_CMD.${_t_}})
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
${_TOOLS_VARNAME.${_t_}}= ${TOOLS_REAL_CMD.${_t_}}
. endif
. endfor
. endif
. endif
.endif
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 !defined(TOOLS_IGNORE.gawk) && !empty(USE_TOOLS:Mgawk)
. if !empty(PKGPATH:Mlang/gawk)
MAKEFLAGS+= TOOLS_IGNORE.gawk=
. elif !empty(_TOOLS_USE_PKGSRC.gawk:M[yY][eE][sS])
${TOOLS_DEPENDS.gawk}+= gawk>=3.1.1:../../lang/gawk
TOOLS_SYMLINK+= gawk
TOOLS_REAL_CMD.gawk= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}awk
. if exists(${TOOLS_REAL_CMD.gawk})
${_TOOLS_VARNAME.gawk}= ${TOOLS_REAL_CMD.gawk}
. endif
. 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
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 !defined(TOOLS_IGNORE.gm4) && !empty(USE_TOOLS:Mgm4)
. if !empty(PKGPATH:Mdevel/m4)
MAKEFLAGS+= TOOLS_IGNORE.gm4=
. elif !empty(_TOOLS_USE_PKGSRC.gm4:M[yY][eE][sS])
${TOOLS_DEPENDS.gm4}+= m4>=1.4:../../devel/m4
TOOLS_SYMLINK+= gm4
TOOLS_REAL_CMD.gm4= ${LOCALBASE}/bin/gm4
. if exists(${TOOLS_REAL_CMD.gm4})
${_TOOLS_VARNAME.gm4}= ${TOOLS_REAL_CMD.gm4}
. endif
. 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
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(TOOLS_IGNORE.gmake) && !empty(USE_TOOLS:Mgmake)
. 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])
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
${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
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
. if exists(${TOOLS_REAL_CMD.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_VARNAME.gmake}= ${TOOLS_REAL_CMD.gmake}
. endif
. endif
.endif
Sort the tool-specific sections for easier browsing.
2005-04-26 21:15:38 +02:00
.if !defined(TOOLS_IGNORE.gsed) && !empty(USE_TOOLS:Mgsed)
. if !empty(PKGPATH:Mtextproc/sed)
MAKEFLAGS+= TOOLS_IGNORE.gsed=
. elif !empty(_TOOLS_USE_PKGSRC.gsed:M[yY][eE][sS])
${TOOLS_DEPENDS.gsed}+= gsed>=3.0.2:../../textproc/gsed
TOOLS_SYMLINK+= gsed
TOOLS_REAL_CMD.gsed= ${LOCALBASE}/bin/${GNU_PROGRAM_PREFIX}sed
. if exists(${TOOLS_REAL_CMD.gsed})
${_TOOLS_VARNAME.gsed}= ${TOOLS_REAL_CMD.gsed}
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
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
Teach replace.mk about GTAR and PAX (replace with archivers/pax if necessary).
2005-04-27 05:41:17 +02:00
.if (!defined(TOOLS_IGNORE.gtar) && \
!defined(TOOLS_IGNORE.pax)) && \
(!empty(USE_TOOLS:Mgtar) || \
!empty(USE_TOOLS:Mpax))
_TOOLS_PAXUTILS= gtar pax
. if !empty(PKGPATH:Marchivers/pax)
. for _t_ in ${_TOOLS_PAXUTILS}
MAKEFLAGS+= TOOLS_IGNORE.${_t_}=
. endfor
. else
. for _t_ in ${_TOOLS_PAXUTILS}
. if empty(USE_TOOLS:M${_t_})
USE_TOOLS+= ${_t_}
. endif
. endfor
. if !empty(_TOOLS_USE_PKGSRC.gtar:M[yY][eE][sS]) || \
!empty(_TOOLS_USE_PKGSRC.pax: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.
#
#${TOOLS_DEPENDS.pax}+= pax>=20040802:../../archivers/pax
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
TOOLS_REAL_CMD.pax= ${LOCALBASE}/bin/pax
. for _t_ in ${_TOOLS_PAXUTILS}
_TOOLS_USE_PKGSRC.${_t_}= yes
TOOLS_SYMLINK+= ${_t_}
. if defined(_TOOLS_VARNAME.${_t_}) && exists(${TOOLS_REAL_CMD.${_t_}})
${_TOOLS_VARNAME.${_t_}}= ${TOOLS_REAL_CMD.${_t_}}
. endif
. endfor
. endif
. endif
TOOLS_CMD.gtar= ${TOOLS_DIR}/bin/tar
.endif
Fix conditions on grep and gzip so that if any of the TOOLS_IGNORE.* are defined for their respective utilities, then we skip the processing to avoid dependency loops.
2005-04-26 23:56:13 +02:00
.if (!defined(TOOLS_IGNORE.gunzip) && \
!defined(TOOLS_IGNORE.gzcat) && \
!defined(TOOLS_IGNORE.gzip)) && \
(!empty(USE_TOOLS:Mgunzip) || \
!empty(USE_TOOLS:Mgzcat) || \
!empty(USE_TOOLS:Mgzip))
Make some code more cut-n-paste-friendly for packages that replace lots of tools.
2005-04-27 00:10:53 +02:00
_TOOLS_GZIPUTILS= gunzip gzcat gzip
Teach replace.mk about gzip, gunzip, and gzcat.
2005-04-24 05:59:44 +02:00
. if !empty(PKGPATH:Marchiver/gzip-base)
Make some code more cut-n-paste-friendly for packages that replace lots of tools.
2005-04-27 00:10:53 +02:00
. for _t_ in ${_TOOLS_GZIPUTILS}
MAKEFLAGS+= TOOLS_IGNORE.${_t_}=
. endfor
Teach replace.mk about gzip, gunzip, and gzcat.
2005-04-24 05:59:44 +02:00
. else
Make some code more cut-n-paste-friendly for packages that replace lots of tools.
2005-04-27 00:10:53 +02:00
. for _t_ in ${_TOOLS_GZIPUTILS}
Teach replace.mk about gzip, gunzip, and gzcat.
2005-04-24 05:59:44 +02:00
. if empty(USE_TOOLS:M${_t_})
USE_TOOLS+= ${_t_}
. endif
. endfor
. if !empty(_TOOLS_USE_PKGSRC.gunzip:M[yY][eE][sS]) || \
!empty(_TOOLS_USE_PKGSRC.gzcat:M[yY][eE][sS]) || \
!empty(_TOOLS_USE_PKGSRC.gzip:M[yY][eE][sS])
${TOOLS_DEPENDS.gzip}+= gzip-base>=1.2.4b:../../archivers/gzip-base
Continue the work in previous commit by making the code more cut-n-paste-friendly for packages with large numbers of utilities.
2005-04-27 00:18:14 +02:00
. for _t_ in ${_TOOLS_GZIPUTILS}
If we're using one of the package's utilities, we're going to be using them all, so make sure _TOOLS_USE_PKGSRC.* is set to "yes".
2005-04-27 00:20:42 +02:00
_TOOLS_USE_PKGSRC.${_t_}= yes
Continue the work in previous commit by making the code more cut-n-paste-friendly for packages with large numbers of utilities.
2005-04-27 00:18:14 +02:00
TOOLS_SYMLINK+= ${_t_}
TOOLS_REAL_CMD.${_t_}= ${LOCALBASE}/bin/${_t_}
To avoid errors, check that there is a TOOL variable associated with the tool before we set it.
2005-04-27 00:51:00 +02:00
. if defined(_TOOLS_VARNAME.${_t_}) && exists(${TOOLS_REAL_CMD.${_t_}})
Continue the work in previous commit by making the code more cut-n-paste-friendly for packages with large numbers of utilities.
2005-04-27 00:18:14 +02:00
${_TOOLS_VARNAME.${_t_}}= ${TOOLS_REAL_CMD.${_t_}}
. endif
. endfor
Teach replace.mk about gzip, gunzip, and gzcat.
2005-04-24 05:59:44 +02:00
. endif
. endif
.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(TOOLS_IGNORE.lex) && !empty(USE_TOOLS:Mlex)
. 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"
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
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
. if exists(${TOOLS_REAL_CMD.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_VARNAME.lex}= ${TOOLS_REAL_CMD.lex}
. endif
. endif
.endif
Teach replace about mtree/MTREE.
2005-04-27 08:15:53 +02:00
.if !defined(TOOLS_IGNORE.mtree) && !empty(USE_TOOLS:Mmtree)
. 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.
#
#${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
. if exists(${TOOLS_REAL_CMD.mtree})
${_TOOLS_VARNAME.mtree}= ${TOOLS_REAL_CMD.mtree}
. endif
. endif
.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(TOOLS_IGNORE.patch) && !empty(USE_TOOLS:Mpatch)
. 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])
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
${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
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
. if exists(${TOOLS_REAL_CMD.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_VARNAME.patch}= ${TOOLS_REAL_CMD.patch}
. endif
. endif
.endif
.if !defined(TOOLS_IGNORE.perl) && !empty(USE_TOOLS:Mperl)
. if !empty(PKGPATH:Mlang/perl5)
MAKEFLAGS+= TOOLS_IGNORE.perl=
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.perl:M[yY][eE][sS])
. include "../../lang/perl5/buildlink3.mk"
TOOLS_SYMLINK+= perl
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.perl= ${LOCALBASE}/bin/perl
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
. if exists(${TOOLS_REAL_CMD.perl})
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_VARNAME.perl}= ${TOOLS_REAL_CMD.perl}
. endif
. endif
.endif
Teach replace.mk about replacements for SH (shells/pdksh) and SHLOCK (pkgtools/shlock).
2005-04-27 06:47:41 +02:00
.if !defined(TOOLS_IGNORE.sh) && !empty(USE_TOOLS:Msh)
. if !empty(PKGPATH:Mshells/pdksh)
MAKEFLAGS+= TOOLS_IGNORE.sh=
. elif !empty(_TOOLS_USE_PKGSRC.sh:M[yY][eE][sS])
${TOOLS_DEPENDS.sh}+= pdksh>=5.2.14:../../shells/pdksh
TOOLS_SYMLINK+= sh
TOOLS_REAL_CMD.sh= ${LOCALBASE}/bin/pdksh
. if exists(${TOOLS_REAL_CMD.sh})
${_TOOLS_VARNAME.sh}= ${TOOLS_REAL_CMD.sh}
. endif
. endif
TOOLS_CMD.sh= ${TOOLS_DIR}/bin/sh
.endif
.if !defined(TOOLS_IGNORE.shlock) && !empty(USE_TOOLS:Mshlock)
. if !empty(PKGPATH:Mpkgtools/shlock)
MAKEFLAGS+= TOOLS_IGNORE.shlock=
. elif !empty(_TOOLS_USE_PKGSRC.shlock:M[yY][eE][sS])
${TOOLS_DEPENDS.shlock}+= shlock>=20020114:../../pkgtools/shlock
TOOLS_SYMLINK+= shlock
TOOLS_REAL_CMD.shlock= ${LOCALBASE}/bin/shlock
. if exists(${TOOLS_REAL_CMD.shlock})
${_TOOLS_VARNAME.shlock}= ${TOOLS_REAL_CMD.shlock}
. endif
. endif
.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(TOOLS_IGNORE.tbl) && !empty(USE_TOOLS:Mtbl)
. 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])
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
${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
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
. if exists(${TOOLS_REAL_CMD.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_VARNAME.tbl}= ${TOOLS_REAL_CMD.tbl}
. endif
. endif
.endif
.if !defined(TOOLS_IGNORE.yacc) && !empty(USE_TOOLS:Myacc)
. 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])
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
${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
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
. if exists(${TOOLS_REAL_CMD.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_VARNAME.yacc}= ${TOOLS_REAL_CMD.yacc} ${TOOLS_ARGS.yacc}
. endif
. endif
.endif
######################################################################
# 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
# PLATFORM_TOOL.<tool> is defined. If it is, then use that as the path
Fix typo.
2005-04-26 21:01:30 +02:00
# to the real command and extract any arguments into TOOLS_ARGS.<tool>.
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
# We also create either a wrapper or a symlink depending on whether
# there are any arguments or not. If PLATFORM_TOOL.<tool> is undefined
Fix typo.
2005-04-27 07:07:57 +02:00
# or empty, then we fall back to checking if TOOL is defined. 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
#
.for _t_ in ${_TOOLS_REPLACE_LIST}
. if !defined(TOOLS_IGNORE.${_t_}) && !empty(USE_TOOLS:M${_t_}) && \
!empty(_TOOLS_USE_PKGSRC.${_t_}:M[nN][oO])
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
. if defined(PLATFORM_TOOL.${_t_}) && !empty(PLATFORM_TOOL.${_t_})
TOOLS_REAL_CMD.${_t_}?= \
${PLATFORM_TOOL.${_t_}:C/^/_asdf_/1:M_asdf_*:S/^_asdf_//}
TOOLS_ARGS.${_t_}?= \
${PLATFORM_TOOL.${_t_}:C/^/_asdf_/1:N_asdf_*}
${_TOOLS_VARNAME.${_t_}}= ${PLATFORM_TOOL.${_t_}}
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
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
. elif defined(${_TOOLS_VARNAME.${_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_REAL_CMD.${_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_VARNAME.${_t_}}:C/^/_asdf_/1:M_asdf_*:S/^_asdf_//}
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_ARGS.${_t_}?= \
${${_TOOLS_VARNAME.${_t_}}:C/^/_asdf_/1:N_asdf_*}
. if !empty(TOOLS_ARGS.${_t_})
TOOLS_WRAP+= ${_t_}
. else
TOOLS_SYMLINK+= ${_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
. 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