summaryrefslogtreecommitdiff
path: root/mk/tools/autoconf.mk
AgeCommit message (Collapse)AuthorFilesLines
2009-03-17Replaced _PKG_SILENT and _PKG_DEBUG with RUN.rillig1-2/+2
2006-12-15Remove trailing tabs.martti1-2/+2
2005-07-17Rename the following variables for brevity:jlam1-14/+14
TOOLS_REAL_CMD.<tool> => TOOLS_PATH.<tool> TOOLS_REAL_ARGS.<tool> => TOOLS_ARGS.<tool> TOOLS_REAL_CMDLINE.<tool> => TOOLS_CMDLINE.<tool>
2005-07-15Drop support for TOOLS_DEPMETHOD.<tool>. The new way to specify ajlam1-10/+19
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-06-11Remove unnecessary .undef lines after .for loops as the loop variablesjlam1-4/+1
are automatically undefined after the loop exits.
2005-06-01Remove mk/autoconf.mk and mk/automake.mk and replace their usage withjlam1-15/+1
USE_TOOLS and any of "autoconf", "autoconf213", "automake" or "automake14". Also, we don't need to call the auto* tools via ${ACLOCAL}, ${AUTOCONF}, etc., since the tools framework takes care to symlink the correct tool to the correct name, so we can just use aclocal, autoconf, etc.
2005-05-21Grammar 101 -- sentences should end in a period.jlam1-2/+2
2005-05-21Add TNF copyright to the new tools framework makefiles.jlam1-1/+37
2005-05-16In the autoconf213 case, the AUTO* variables should point to thejlam1-4/+4
TOOLS_CMD.* variables for the -2.13 variants. Otherwise, they're empty, which causes errors for packages that use ${AUTOCONF}.
2005-05-11Rewrite so that we avoid needing to check the value of TOOLS_REAL_CMD.*jlam1-61/+62
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-10TOOLS_CREATE has replaced TOOLS_{SYMLINK,WRAP}.jlam1-2/+2
2005-04-28Define TOOLS_DEPENDS.* to be the dependency that will be added, andjlam1-3/+13
filter out dependencies that have already been added.
2005-04-26As of bsd.tool.mk:1.6, TOOLS_CMD.<tool> defaults tojlam1-14/+1
${TOOLS_DIR}/bin/<tool>, so remove redundant settings.
2005-04-15Avoid dependency loops by setting and checking TOOLS_IGNORE.* guards.jlam1-4/+12
2005-04-15Initial commit of the new tools framework. This is currently designedjlam1-0/+184
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.