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

186 lines
6.4 KiB
Makefile
Raw Normal View History

Deprecate unused BUILD_USES_GETTEXT_M4 variable.
2007-03-01 23:29:15 +01:00
# $NetBSD: automake.mk,v 1.18 2007/03/01 22:29:15 wiz Exp $
Add TNF copyright to the new tools framework makefiles.
2005-05-21 06:46:52 +02:00
#
# Copyright (c) 2005 The NetBSD Foundation, Inc.
# All rights reserved.
#
# This code is derived from software contributed to The NetBSD Foundation
Grammar 101 -- sentences should end in a period.
2005-05-21 06:53:17 +02:00
# by Johnny C. Lam.
Add TNF copyright to the new tools framework makefiles.
2005-05-21 06:46:52 +02:00
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
# are met:
# 1. Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# 2. Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the distribution.
# 3. All advertising materials mentioning features or use of this software
# must display the following acknowledgement:
# This product includes software developed by the NetBSD
# Foundation, Inc. and its contributors.
# 4. Neither the name of The NetBSD Foundation nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
# ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
# TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
# PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
# CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
# ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGE.
#
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
#
# This Makefile fragment handles packages that use GNU automake.
#
# By default, all of the automake-related scripts are marked as
# "missing" by running the GNU missing script in place of the utility.
# This hides the automake-related scripts from makefiles that aggressively
# call them when some of the inputs are modified in ways the makefiles
# don't expect.
#
# If a package needs to use GNU automake, then the package Makefile
# should contain one of the following lines:
#
# USE_TOOLS+= automake # use recent GNU automake (>=1.9)
# USE_TOOLS+= automake14 # use GNU automake ~1.4
#
# This will allow the package to invoke "aclocal" and "automake" by
# their usual, bare names.
#
# If a particular minimum version of automake is required, then the
# package Makefile can additionally set AUTOMAKE_REQD to the desired
# version, e.g.:
#
# AUTOMAKE_REQD= 1.8 # use at least automake>=1.8
#
# If a package additionally needs to regenerate configure scripts and
# Makefiles that use gettext, then the package Makefile should contain
# the following line:
#
# USE_TOOLS+= gettext-m4 # need gettext.m4 to re-gen files
#
# To globally prevent any GNU automake handling, set the following
# in the package Makefile:
#
# AUTOMAKE_OVERRIDE= no
#
# Only allow one of "automake" and "automake14" in USE_TOOLS.
Drop support for TOOLS_DEPMETHOD.<tool>. The new way to specify a run-time dependency (DEPENDS) on a tool is to append a ":run" modifier to the tool name, e.g., USE_TOOLS+= perl:run Tools without modifiers or with an explicit ":build" modifier will cause build dependencies (BUILD_DEPENDS) on those tools to be added. This makes the notation a bit more compact.
2005-07-15 22:14:02 +02:00
.if !empty(USE_TOOLS:C/:.*//:Mautomake) && \
!empty(USE_TOOLS:C/:.*//:Mautomake14)
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
PKG_FAIL_REASON+= "\`\`automake'' and \`\`automake14'' conflict in USE_TOOLS."
.endif
# This is an exhaustive list of all of the scripts supplied by GNU
# automake.
#
Rewrite so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
_TOOLS_AM_NAMES= aclocal aclocal-1.4 \
aclocal-1.5 \
aclocal-1.6 \
aclocal-1.7 \
aclocal-1.8 \
Recognize aclocal-1.10 and automake-1.10.
2006-12-05 23:48:31 +01:00
aclocal-1.9 \
aclocal-1.10
Rewrite so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
_TOOLS_AM_NAMES+= automake automake-1.4 \
automake-1.5 \
automake-1.6 \
automake-1.7 \
automake-1.8 \
Recognize aclocal-1.10 and automake-1.10.
2006-12-05 23:48:31 +01:00
automake-1.9 \
automake-1.10
Rewrite so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
.for _t_ in ${_TOOLS_AM_NAMES}
_TOOLS_AM_TYPE.${_t_}?= TOOLS_GNU_MISSING
.endfor
Initial commit of the new tools framework. This is currently designed to be a drop-in replacement for mk/tools.mk, but isn't yet enabled pending further testing. To use, edit bsd.pkg.mk to include bsd.tools.mk instead of tools.mk. The major changes from the old tools framework are: (1) The new interface to using the tools framework is through setting USE_TOOLS in the package Makefile, e.g., USE_TOOLS+= autoconf gmake yacc (2) Bison/yacc handling is improved. Instead of adding checks for /usr/bin/yacc to the package Makefile and explicitly setting YACC, e.g., security/mit-krb5/Makefile, simply add "yacc" to USE_TOOLS. If bison is explicitly required, then add "bison" to USE_TOOLS instead. (3) GNU auto* tools are handled differently. "autoconf", "aclocal", "automake", etc. will be tools in ${TOOLS_DIR} that point to the correct versions of the auto* tools. Instead of patching Makefiles or scripts to use ${AUTOCONF}, ${ACLOCAL}, etc., the correct versions of the tools will be called if they are invoked simply by their bare names. This is selected by adding either "autoconf" or "autoconf213", or "automake" or "automake14" to USE_TOOLS. The new tools framework will deprecate the following variables: ACLOCAL AUTORECONF AUTOCONF BUILD_USES_GETTEXT_M4 AUTOHEADER USE_GNU_TOOLS AUTOMAKE USE_TBL The new tools framework will deprecate the following *.mk files: mk/autoconf.mk mk/automake.mk mk/tools.mk Additional documentation on how to use bsd.tools.mk to create new tools under ${TOOLS_DIR} may be found in the header comments in bsd.tools.mk.
2005-04-15 02:00:21 +02:00
Drop support for TOOLS_DEPMETHOD.<tool>. The new way to specify a run-time dependency (DEPENDS) on a tool is to append a ":run" modifier to the tool name, e.g., USE_TOOLS+= perl:run Tools without modifiers or with an explicit ":build" modifier will cause build dependencies (BUILD_DEPENDS) on those tools to be added. This makes the notation a bit more compact.
2005-07-15 22:14:02 +02:00
.if !defined(TOOLS_IGNORE.automake) && !empty(USE_TOOLS:C/:.*//:Mautomake)
Avoid dependency loops by setting and checking TOOLS_IGNORE.* guards.
2005-04-15 07:30:48 +02:00
. if !empty(PKGPATH:Mdevel/automake)
MAKEFLAGS+= TOOLS_IGNORE.automake=
. else
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
AUTOMAKE_REQD?= 1.9
Needing automake implies needing autoconf. Match the version requirements outlined in mk/automake.mk.
2005-05-11 22:21:32 +02:00
AUTOCONF_REQD?= 2.58
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
Drop support for TOOLS_DEPMETHOD.<tool>. The new way to specify a run-time dependency (DEPENDS) on a tool is to append a ":run" modifier to the tool name, e.g., USE_TOOLS+= perl:run Tools without modifiers or with an explicit ":build" modifier will cause build dependencies (BUILD_DEPENDS) on those tools to be added. This makes the notation a bit more compact.
2005-07-15 22:14:02 +02:00
. if !empty(USE_TOOLS:Mautomake\:run)
_TOOLS_DEPMETHOD.automake= DEPENDS
. else
_TOOLS_DEPMETHOD.automake= BUILD_DEPENDS
. endif
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.automake?= automake>=${AUTOMAKE_REQD}:../../devel/automake
Drop support for TOOLS_DEPMETHOD.<tool>. The new way to specify a run-time dependency (DEPENDS) on a tool is to append a ":run" modifier to the tool name, e.g., USE_TOOLS+= perl:run Tools without modifiers or with an explicit ":build" modifier will cause build dependencies (BUILD_DEPENDS) on those tools to be added. This makes the notation a bit more compact.
2005-07-15 22:14:02 +02:00
. if empty(${_TOOLS_DEPMETHOD.automake}:M${TOOLS_DEPENDS.automake})
${_TOOLS_DEPMETHOD.automake}+= ${TOOLS_DEPENDS.automake}
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
. endif
Rewrite so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
EVAL_PREFIX+= _TOOLS_AM_PREFIX=automake
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 so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
_TOOLS_AM_TYPE.aclocal= TOOLS_CREATE
Rename the following variables for brevity: TOOLS_REAL_CMD.<tool> => TOOLS_PATH.<tool> TOOLS_REAL_ARGS.<tool> => TOOLS_ARGS.<tool> TOOLS_REAL_CMDLINE.<tool> => TOOLS_CMDLINE.<tool>
2005-07-17 23:36:24 +02:00
TOOLS_PATH.aclocal= ${_TOOLS_AM_PREFIX}/bin/aclocal
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 so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
_TOOLS_AM_TYPE.automake= TOOLS_CREATE
Rename the following variables for brevity: TOOLS_REAL_CMD.<tool> => TOOLS_PATH.<tool> TOOLS_REAL_ARGS.<tool> => TOOLS_ARGS.<tool> TOOLS_REAL_CMDLINE.<tool> => TOOLS_CMDLINE.<tool>
2005-07-17 23:36:24 +02:00
TOOLS_PATH.automake= ${_TOOLS_AM_PREFIX}/bin/automake
Avoid dependency loops by setting and checking TOOLS_IGNORE.* guards.
2005-04-15 07:30: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
Drop support for TOOLS_DEPMETHOD.<tool>. The new way to specify a run-time dependency (DEPENDS) on a tool is to append a ":run" modifier to the tool name, e.g., USE_TOOLS+= perl:run Tools without modifiers or with an explicit ":build" modifier will cause build dependencies (BUILD_DEPENDS) on those tools to be added. This makes the notation a bit more compact.
2005-07-15 22:14:02 +02:00
.if !defined(TOOLS_IGNORE.automake14) && !empty(USE_TOOLS:C/:.*//:Mautomake14)
Avoid dependency loops by setting and checking TOOLS_IGNORE.* guards.
2005-04-15 07:30:48 +02:00
. if !empty(PKGPATH:Mdevel/automake14)
MAKEFLAGS+= TOOLS_IGNORE.automake14=
. else
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
AUTOMAKE_REQD?= 1.4
Needing automake implies needing autoconf. Match the version requirements outlined in mk/automake.mk.
2005-05-11 22:21:32 +02:00
AUTOCONF_REQD?= 2.13
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
Drop support for TOOLS_DEPMETHOD.<tool>. The new way to specify a run-time dependency (DEPENDS) on a tool is to append a ":run" modifier to the tool name, e.g., USE_TOOLS+= perl:run Tools without modifiers or with an explicit ":build" modifier will cause build dependencies (BUILD_DEPENDS) on those tools to be added. This makes the notation a bit more compact.
2005-07-15 22:14:02 +02:00
. if !empty(USE_TOOLS:Mautomake14\:run)
_TOOLS_DEPMETHOD.automake14= DEPENDS
. else
_TOOLS_DEPMETHOD.automake14= BUILD_DEPENDS
. endif
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
TOOLS_DEPENDS.automake14?= automake14>=${AUTOMAKE_REQD}:../../devel/automake14
Drop support for TOOLS_DEPMETHOD.<tool>. The new way to specify a run-time dependency (DEPENDS) on a tool is to append a ":run" modifier to the tool name, e.g., USE_TOOLS+= perl:run Tools without modifiers or with an explicit ":build" modifier will cause build dependencies (BUILD_DEPENDS) on those tools to be added. This makes the notation a bit more compact.
2005-07-15 22:14:02 +02:00
. if empty(${_TOOLS_DEPMETHOD.automake14}:M${TOOLS_DEPENDS.automake14})
${_TOOLS_DEPMETHOD.automake14}+= ${TOOLS_DEPENDS.automake14}
Define TOOLS_DEPENDS.* to be the dependency that will be added, and filter out dependencies that have already been added.
2005-04-28 05:01:11 +02:00
. endif
Rewrite so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
EVAL_PREFIX+= _TOOLS_AM_PREFIX=automake14
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 so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
_TOOLS_AM_TYPE.aclocal-1.4= TOOLS_CREATE
_TOOLS_AM_TYPE.aclocal= # empty
Rename the following variables for brevity: TOOLS_REAL_CMD.<tool> => TOOLS_PATH.<tool> TOOLS_REAL_ARGS.<tool> => TOOLS_ARGS.<tool> TOOLS_REAL_CMDLINE.<tool> => TOOLS_CMDLINE.<tool>
2005-07-17 23:36:24 +02:00
TOOLS_PATH.aclocal-1.4= ${_TOOLS_AM_PREFIX}/bin/aclocal-1.4
Rewrite so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
TOOLS_ALIASES.aclocal-1.4= aclocal
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 so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
_TOOLS_AM_TYPE.automake-1.4= TOOLS_CREATE
_TOOLS_AM_TYPE.automake= # empty
Rename the following variables for brevity: TOOLS_REAL_CMD.<tool> => TOOLS_PATH.<tool> TOOLS_REAL_ARGS.<tool> => TOOLS_ARGS.<tool> TOOLS_REAL_CMDLINE.<tool> => TOOLS_CMDLINE.<tool>
2005-07-17 23:36:24 +02:00
TOOLS_PATH.automake-1.4= ${_TOOLS_AM_PREFIX}/bin/automake-1.4
Rewrite so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
TOOLS_ALIASES.automake-1.4= automake
Avoid dependency loops by setting and checking TOOLS_IGNORE.* guards.
2005-04-15 07:30: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
Based on the value of ${AUTOCONF_REQD}, choose the right autoconf tool to use. This fixes packages that want automake-1.4, but autoconf-2.50.
2005-05-20 04:40:23 +02:00
# Discover which version of autoconf should be used with automake.
Only add the autoconf tool if the user also requested automake. This avoids making autoconf required by every package in pkgsrc.
2005-05-20 05:08:45 +02:00
.if !empty(USE_TOOLS:Mautomake) || !empty(USE_TOOLS:Mautomake14)
. if !defined(_TOOLS_AM_AUTOCONF)
Based on the value of ${AUTOCONF_REQD}, choose the right autoconf tool to use. This fixes packages that want automake-1.4, but autoconf-2.50.
2005-05-20 04:40:23 +02:00
_TOOLS_AM_AUTOCONF!= \
Properly quote dependency to avoid creating garbage files in the pkgsrc tree.
2005-05-20 04:57:23 +02:00
dep="autoconf>="${AUTOCONF_REQD:Q}; \
if ${PKG_ADMIN} pmatch "$$dep" autoconf-2.13; then \
Based on the value of ${AUTOCONF_REQD}, choose the right autoconf tool to use. This fixes packages that want automake-1.4, but autoconf-2.50.
2005-05-20 04:40:23 +02:00
${ECHO} "autoconf213"; \
else \
${ECHO} "autoconf"; \
fi
Only add the autoconf tool if the user also requested automake. This avoids making autoconf required by every package in pkgsrc.
2005-05-20 05:08:45 +02:00
. endif
Based on the value of ${AUTOCONF_REQD}, choose the right autoconf tool to use. This fixes packages that want automake-1.4, but autoconf-2.50.
2005-05-20 04:40:23 +02:00
MAKEVARS+= _TOOLS_AM_AUTOCONF
USE_TOOLS+= ${_TOOLS_AM_AUTOCONF}
Only add the autoconf tool if the user also requested automake. This avoids making autoconf required by every package in pkgsrc.
2005-05-20 05:08:45 +02:00
.endif
Based on the value of ${AUTOCONF_REQD}, choose the right autoconf tool to use. This fixes packages that want automake-1.4, but autoconf-2.50.
2005-05-20 04:40:23 +02:00
Rewrite so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
# If the package wants to override the GNU auto* tools, then do it.
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
AUTOMAKE_OVERRIDE?= yes
.if !empty(AUTOMAKE_OVERRIDE:M[yY][eE][sS])
Rewrite so that we avoid needing to check the value of TOOLS_REAL_CMD.* within make. This allows us to use EVAL_PREFIX to locate the installation prefix for autoconf and automake, which is more pkgviews-friendly. In any case, this implementation is a lot simpler anyway.
2005-05-11 22:09:44 +02:00
. for _t_ in ${_TOOLS_AM_NAMES}
. if !empty(_TOOLS_AM_TYPE.${_t_})
${_TOOLS_AM_TYPE.${_t_}}+= ${_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
. endfor
.endif
.if !empty(USE_TOOLS:Mgettext-m4)
BUILD_DEPENDS+= {gettext-0.10.35nb1,gettext-m4-[0-9]*}:../../devel/gettext-m4
.endif
Reference in a new issue Copy permalink