kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/Mk/bsd.autotools.mk

415 lines
13 KiB
Makefile
Raw Normal View History

Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
#-*- mode: makefile; tab-width: 4; -*-
# ex:ts=4
#
# $FreeBSD$
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
# Please view me with 4 column tabs!
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
# Please make sure all changes to this file are passed either through
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
# the maintainer, or portmgr@FreeBSD.org
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
Autotools_Include_MAINTAINER= ade@FreeBSD.org
Purge WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN The versioned autotools are now strictly for building other ports in the tree. Likewise, the gnu- autotools are for runtime dependencies for IDEs, and others, where unmodified cross-platform capabilities are desired.
2005-06-16 19:29:45 +02:00
#---------------------------------------------------------------------------
# IMPORTANT! READ ME! YES, THAT MEANS YOU!
#
# The "versioned" autotools referenced here are for BUILDING other ports
# only. THIS CANNOT BE STRESSED HIGHLY ENOUGH. Things WILL BREAK if you
# try to use them for anything other than ports/ work. This particularly
# includes use as a run-time dependency.
#
# If you need unmodified versions of autotools, such as for use in an
# IDE, then you MUST use the devel/gnu-* equivalents, and NOT these.
# See devel/anjuta and devel/kdevelop for examples.
#
# You have been WARNED!
#---------------------------------------------------------------------------
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#---------------------------------------------------------------------------
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# Compatibility shims for the old method of using autotools. These are
# slated for removal on January 1st 2006
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#---------------------------------------------------------------------------
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
USE_AUTOTOOLS_COMPAT=
.if defined(USE_AUTOMAKE_VER)
USE_AUTOTOOLS_COMPAT+= automake:${USE_AUTOMAKE_VER}
.endif
.if defined(WANT_AUTOMAKE_VER)
USE_AUTOTOOLS_COMPAT+= automake:${WANT_AUTOMAKE_VER}:env
.endif
.if defined(USE_ACLOCAL_VER)
USE_AUTOTOOLS_COMPAT+= aclocal:${USE_ACLOCAL_VER}
.endif
.if defined(USE_AUTOHEADER_VER)
USE_AUTOTOOLS_COMPAT+= autoheader:${USE_AUTOHEADER_VER}
.endif
.if defined(USE_AUTOCONF_VER)
USE_AUTOTOOLS_COMPAT+= autoconf:${USE_AUTOCONF_VER}
.endif
.if defined(WANT_AUTOCONF_VER)
USE_AUTOTOOLS_COMPAT+= autoconf:${WANT_AUTOCONF_VER}:env
.endif
.if defined(USE_LIBLTDL)
USE_AUTOTOOLS_COMPAT+= libltdl:15
.endif
.if defined(USE_LIBTOOL_VER)
USE_AUTOTOOLS_COMPAT+= libtool:${USE_LIBTOOL_VER}
.endif
.if defined(USE_INC_LIBTOOL_VER)
USE_AUTOTOOLS_COMPAT+= libtool:${USE_INC_LIBTOOL_VER}:inc
.endif
.if defined(WANT_LIBTOOL_VER)
USE_AUTOTOOLS_COMPAT+= libtool:${WANT_LIBTOOL_VER}:env
.endif
# Ensure that we're not mixing and matching old and new systems
Remove trailing spaces.
2005-01-09 11:12:07 +01:00
#
Instead of checking to see if USE_AUTOTOOLS_COMPAT is defined, ensure that it is empty. USE_AUTOTOOLS_COMPAT will always be defined, but we don't want to assume that we're using autotools compatibility unless its value is non-null. Previously, the defined check would cause ports using the new USE_AUTOTOOLS scheme to fail. Approved by: ade
2005-07-02 07:02:24 +02:00
.if ${USE_AUTOTOOLS_COMPAT}!=""
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. if defined(USE_AUTOTOOLS)
BROKEN+= "Mix and match of old and new autotools system prohibited"
. else
USE_AUTOTOOLS= ${USE_AUTOTOOLS_COMPAT}
Add a pre-everything:: target that will print out appropriate warnings if a port is still using the old autotools Makefile constructs. For example: *** AUTOTOOLS WARNING for x11/electricsheep This port is using old autotools constructs which wil be disappearing on 1st January 2006 In most cases, this warning can be fixed by removing all the old constructs and replacing them with: USE_AUTOTOOLS= libtool:13 The first line should be easily parseable by portbuild and tinderbox clusters to flag such ports. I'll be doing a few more sweeps of the ports tree to pick up on any such ports over the coming weeks, before turning off the old system and marking the port BROKEN in such cases.
2005-11-19 23:04:25 +01:00
_AUTOTOOLS_PN= ${.CURDIR:C/${PORTSDIR}\///}
pre-everything::
@${ECHO} "*** AUTOTOOLS WARNING for ${_AUTOTOOLS_PN}"
@${ECHO} This port is using old autotools constructs which wil be"
@${ECHO} "disappearing on 1st January 2006"
@${ECHO} ""
@${ECHO} "In most cases, this warning can be fixed by removing"
@${ECHO} "all the old constructs and replacing them with:"
@${ECHO} " USE_AUTOTOOLS= ${USE_AUTOTOOLS_COMPAT}"
@${ECHO} ""
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. endif
.endif
#---------------------------------------------------------------------------
# Entry point into the autotools system
#---------------------------------------------------------------------------
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# USE_AUTOTOOLS= tool:version[:inc | :env] ...
Add USE_ACLOCAL_VER= (automake-version), another entry point into using the various GNU autotools, running "aclocal" at configuration time, prior to any other tools. This should allow a number of ports Makefiles to be cleaned up with respect to their explicit calling of ${ACLOCAL} PR: 41945 (reworked for current reality) Submitted by: Bruce M Simpson <bms@spc.org>
2005-06-16 23:52:56 +02:00
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# 'tool' can currently be one of:
# libtool, libltdl, autoconf, autoheader, automake, aclocal
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# 'version' is tool dependent
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# ':inc' is for libtool only, and is used to modify the patch-autotools
# target to use the relevant included version of libtool
Add USE_ACLOCAL_VER= (automake-version), another entry point into using the various GNU autotools, running "aclocal" at configuration time, prior to any other tools. This should allow a number of ports Makefiles to be cleaned up with respect to their explicit calling of ${ACLOCAL} PR: 41945 (reworked for current reality) Submitted by: Bruce M Simpson <bms@spc.org>
2005-06-16 23:52:56 +02:00
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# ':env' is for autoconf/autoheader/automake/aclocal and is used to
# specify that the environment variables are needed, but the relevant
# tool should NOT be run as part of the run-autotools target
#
# XXX: there is currently no sanity checking of the supplied variables
# other than to detect actually available versions. This should
# probably be fixed at some point.
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# In addition, the following variables can be set in the port Makefile
# to be passed to the relevant tools:
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# AUTOMAKE_ARGS=...
# - Extra arguments passed to automake during configure step
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# ACLOCAL_ARGS=...
# - Arguments passed to aclocal during configure step
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#
# AUTOCONF_ARGS=...
# - Extra arguments passed to autoconf during configure step
#
# AUTOHEADER_ARGS=...
# - Extra arguments passed to autoheader during configure step
#
# LIBTOOLFLAGS=<value>
# - Arguments passed to libtool during configure step
# Currently defaults to "--disable-ltlibs", but this will be going
# away when libtool .la files are brought back
#
# LIBTOOLFILES=<list-of-files>
# - A list of files to patch during libtool pre-configuration
# Defaults to "aclocal.m4" if autoconf is in use, otherwise "configure"
#
#---------------------------------------------------------------------------
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# XXX: here be dragons :)
#
.for item in ${USE_AUTOTOOLS}
AUTOTOOL_${item:C/^([^:]+).*/\1/}${item:M*\:*\:*:C/^[^:]+:[^:]+:([^:]+)/_\1/}= ${item:C/^[^:]+:([^:]+).*/\1/}
.endfor
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#---------------------------------------------------------------------------
Add USE_ACLOCAL_VER= (automake-version), another entry point into using the various GNU autotools, running "aclocal" at configuration time, prior to any other tools. This should allow a number of ports Makefiles to be cleaned up with respect to their explicit calling of ${ACLOCAL} PR: 41945 (reworked for current reality) Submitted by: Bruce M Simpson <bms@spc.org>
2005-06-16 23:52:56 +02:00
# AUTOMAKE/ACLOCAL
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#---------------------------------------------------------------------------
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
.if defined(AUTOTOOL_automake)
AUTOTOOL_automake_env= ${AUTOTOOL_automake}
GNU_CONFIGURE?= yes
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
.endif
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
.if defined(AUTOTOOL_aclocal)
AUTOTOOL_automake_env= ${AUTOTOOL_aclocal}
GNU_CONFIGURE?= yes
Add USE_ACLOCAL_VER= (automake-version), another entry point into using the various GNU autotools, running "aclocal" at configuration time, prior to any other tools. This should allow a number of ports Makefiles to be cleaned up with respect to their explicit calling of ${ACLOCAL} PR: 41945 (reworked for current reality) Submitted by: Bruce M Simpson <bms@spc.org>
2005-06-16 23:52:56 +02:00
.endif
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
.if defined(AUTOTOOL_automake_env)
AUTOMAKE_VERSION= ${AUTOTOOL_automake_env}
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
# Make sure we specified a legal version of automake
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. if !exists(${PORTSDIR}/devel/automake${AUTOMAKE_VERSION}/Makefile)
BROKEN+= "Unknown AUTOMAKE version: ${AUTOMAKE_VERSION}"
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
. endif
# Set up the automake environment
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
AUTOMAKE= ${LOCALBASE}/bin/automake${AUTOMAKE_VERSION}
AUTOMAKE_DIR= ${LOCALBASE}/share/automake${AUTOMAKE_VERSION}
ACLOCAL= ${LOCALBASE}/bin/aclocal${AUTOMAKE_VERSION}
ACLOCAL_DIR= ${LOCALBASE}/share/aclocal${AUTOMAKE_VERSION}
AUTOMAKE_PATH= ${LOCALBASE}/libexec/automake${AUTOMAKE_VERSION}:
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
AUTOMAKE_VARS= ACLOCAL=${ACLOCAL} AUTOMAKE=${AUTOMAKE}
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
AUTOMAKE_DEPENDS= ${AUTOMAKE}:${PORTSDIR}/devel/automake${AUTOMAKE_VERSION}
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
BUILD_DEPENDS+= ${AUTOMAKE_DEPENDS}
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# XXX: backwards compatibility shim
#
. if ${AUTOMAKE_VERSION} == 14
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
AUTOMAKE_ARGS+= -i
. endif
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. if defined(AUTOTOOL_aclocal)
Add USE_ACLOCAL_VER= (automake-version), another entry point into using the various GNU autotools, running "aclocal" at configuration time, prior to any other tools. This should allow a number of ports Makefiles to be cleaned up with respect to their explicit calling of ${ACLOCAL} PR: 41945 (reworked for current reality) Submitted by: Bruce M Simpson <bms@spc.org>
2005-06-16 23:52:56 +02:00
ACLOCAL_ARGS?= --acdir=${ACLOCAL_DIR}
. endif
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
.endif
#---------------------------------------------------------------------------
# AUTOCONF/AUTOHEADER
#---------------------------------------------------------------------------
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
.if defined(AUTOTOOL_autoheader)
AUTOTOOL_autoconf= ${AUTOTOOL_autoheader}
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
.endif
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
.if defined(AUTOTOOL_autoconf)
AUTOTOOL_autoconf_env= ${AUTOTOOL_autoconf}
GNU_CONFIGURE?= yes
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
.endif
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
.if defined(AUTOTOOL_autoconf_env)
AUTOCONF_VERSION= ${AUTOTOOL_autoconf_env}
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
# Make sure we specified a legal version of autoconf
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. if !exists(${PORTSDIR}/devel/autoconf${AUTOCONF_VERSION}/Makefile)
BROKEN+= "Unknown AUTOCONF version: ${AUTOCONF_VERSION}"
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
. endif
# Set up the autoconf/autoheader environment
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
AUTOCONF= ${LOCALBASE}/bin/autoconf${AUTOCONF_VERSION}
AUTOCONF_DIR= ${LOCALBASE}/share/autoconf${AUTOCONF_VERSION}
AUTOHEADER= ${LOCALBASE}/bin/autoheader${AUTOCONF_VERSION}
AUTOIFNAMES= ${LOCALBASE}/bin/ifnames${AUTOCONF_VERSION}
AUTOM4TE= ${LOCALBASE}/bin/autom4te${AUTOCONF_VERSION}
AUTORECONF= ${LOCALBASE}/bin/autoreconf${AUTOCONF_VERSION}
AUTOSCAN= ${LOCALBASE}/bin/autoscan${AUTOCONF_VERSION}
AUTOUPDATE= ${LOCALBASE}/bin/autoupdate${AUTOCONF_VERSION}
AUTOCONF_PATH= ${LOCALBASE}/libexec/autoconf${AUTOCONF_VERSION}:
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
AUTOCONF_VARS= AUTOCONF=${AUTOCONF} AUTOHEADER=${AUTOHEADER} AUTOIFNAMES=${AUTOIFNAMES} AUTOM4TE=${AUTOM4TE} AUTORECONF=${AUTORECONF} AUTOSCAN=${AUTOSCAN} AUTOUPDATE=${AUTOUPDATE}
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
AUTOCONF_DEPENDS= ${AUTOCONF}:${PORTSDIR}/devel/autoconf${AUTOCONF_VERSION}
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
BUILD_DEPENDS+= ${AUTOCONF_DEPENDS}
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
.endif
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#---------------------------------------------------------------------------
# LIBTOOL/LIBLTDL
#---------------------------------------------------------------------------
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
# Convenience function to save people having to depend directly on
Switch over to versioned devel/libltdl15 (from devel/libltdl) after repo-copy.
2004-06-08 22:45:00 +02:00
# devel/libltdl15
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
.if defined(AUTOTOOL_libltdl)
Switch over to versioned devel/libltdl15 (from devel/libltdl) after repo-copy.
2004-06-08 22:45:00 +02:00
LIB_DEPENDS+= ltdl.4:${PORTSDIR}/devel/libltdl15
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
.endif
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
.if defined(AUTOTOOL_libtool)
GNU_CONFIGURE?= YES
AUTOTOOL_libtool_env= ${AUTOTOOL_libtool}
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
.endif
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
.if defined(AUTOTOOL_libtool_inc)
GNU_CONFIGURE?= YES
AUTOTOOL_libtool_env= ${AUTOTOOL_libtool_inc}
.endif
.if defined(AUTOTOOL_libtool_env)
LIBTOOL_VERSION= ${AUTOTOOL_libtool_env}
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
# Make sure we specified a legal version of libtool
Remove trailing spaces.
2005-01-09 11:12:07 +01:00
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. if !exists(${PORTSDIR}/devel/libtool${LIBTOOL_VERSION}/Makefile)
BROKEN+= "Unknown LIBTOOL version: ${LIBTOOL_VERSION}"
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
. endif
# Set up the libtool environment
#
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
LIBTOOL= ${LOCALBASE}/bin/libtool${LIBTOOL_VERSION}
LIBTOOLIZE= ${LOCALBASE}/bin/libtoolize${LIBTOOL_VERSION}
LIBTOOL_LIBEXECDIR= ${LOCALBASE}/libexec/libtool${LIBTOOL_VERSION}
LIBTOOL_SHAREDIR= ${LOCALBASE}/share/libtool${LIBTOOL_VERSION}
Autotools cleanup. Remove autoconf257 (259), automake17 (18), and libtool14 (13/15). PR: 67768 Submitted by: ade Approved by: 4-exp bento runs (thanks, kris!)
2004-07-01 19:06:41 +02:00
LIBTOOL_M4= ${LOCALBASE}/share/aclocal/libtool${LIBTOOL_VERSION}.m4
LTMAIN= ${LIBTOOL_SHAREDIR}/ltmain.sh
. if ${LIBTOOL_VERSION} == 13
LTCONFIG= ${LIBTOOL_SHAREDIR}/ltconfig${LIBTOOL_VERSION}
. else
LTCONFIG= ${TRUE}
. endif
LIBTOOL_PATH= ${LIBTOOL_LIBEXECDIR}:
LIBTOOL_VARS= LIBTOOL=${LIBTOOL} LIBTOOLIZE=${LIBTOOLIZE} LIBTOOL_M4=${LIBTOOL_M4} LTCONFIG=${LTCONFIG}
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
LIBTOOL_DEPENDS= ${LIBTOOL}:${PORTSDIR}/devel/libtool${LIBTOOL_VERSION}
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
BUILD_DEPENDS+= ${LIBTOOL_DEPENDS}
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
# XXX: do we really need this?
#
LIBTOOLFLAGS?= --disable-ltlibs
. if defined(AUTOTOOL_autoconf)
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
LIBTOOLFILES?= aclocal.m4
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
. else
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
LIBTOOLFILES?= configure
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
. endif
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
.endif
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#---------------------------------------------------------------------------
# Environmental handling
# Now that we've got our environments defined for autotools, add them
# in so that the rest of the world can handle them
#
AUTOTOOLS_PATH= ${AUTOMAKE_PATH}${AUTOCONF_PATH}${LIBTOOL_PATH}
AUTOTOOLS_VARS= ${AUTOMAKE_VARS} ${AUTOCONF_VARS} ${LIBTOOL_VARS}
.if defined(AUTOTOOLS_PATH) && (${AUTOTOOLS_PATH} != "")
AUTOTOOLS_ENV+= PATH=${AUTOTOOLS_PATH}${PATH}
CONFIGURE_ENV+= PATH=${AUTOTOOLS_PATH}${PATH}
MAKE_ENV+= PATH=${AUTOTOOLS_PATH}${PATH}
SCRIPTS_ENV+= PATH=${AUTOTOOLS_PATH}${PATH}
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. for item in automake aclocal autoconf autoheader libtool
. if defined(AUTOTOOL_${item}_env)
${item:U}_ENV+= PATH=${AUTOTOOLS_PATH}${PATH}
. endif
. endfor
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
.endif
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
.if defined(AUTOTOOLS_VARS) && (${AUTOTOOLS_VARS} != "")
AUTOTOOLS_ENV+= ${AUTOTOOLS_VARS}
CONFIGURE_ENV+= ${AUTOTOOLS_VARS}
MAKE_ENV+= ${AUTOTOOLS_VARS}
SCRIPTS_ENV+= ${AUTOTOOLS_VARS}
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. for item in automake aclocal autoconf autoheader libtool
. if defined(AUTOTOOL_${item}_env)
${item:U}_ENV+= ${AUTOTOOLS_VARS}
. endif
. endfor
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
.endif
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
#---------------------------------------------------------------------------
# Make targets
#---------------------------------------------------------------------------
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
# run-autotools
#
# Part of the configure set - run appropriate programs prior to
Rework the run-autotools target into a series of sub-targets, the order of which can now be overriden. PR: 86309 (slightly reworked) Submitted by: thierry
2005-11-19 00:21:49 +01:00
# the actual configure target if autotools are in use.
# If needed, this target can be overridden, for example to change
# the order of autotools running.
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
.if !target(run-autotools)
Rework the run-autotools target into a series of sub-targets, the order of which can now be overriden. PR: 86309 (slightly reworked) Submitted by: thierry
2005-11-19 00:21:49 +01:00
run-autotools:: run-autotools-aclocal run-autotools-automake \
run-autotools-autoconf run-autotools-autoheader
.endif
.if !target(run-autotools-aclocal)
run-autotools-aclocal:
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. if defined(AUTOTOOL_aclocal)
Add USE_ACLOCAL_VER= (automake-version), another entry point into using the various GNU autotools, running "aclocal" at configuration time, prior to any other tools. This should allow a number of ports Makefiles to be cleaned up with respect to their explicit calling of ${ACLOCAL} PR: 41945 (reworked for current reality) Submitted by: Bruce M Simpson <bms@spc.org>
2005-06-16 23:52:56 +02:00
@(cd ${CONFIGURE_WRKSRC} && ${SETENV} ${AUTOTOOLS_ENV} ${ACLOCAL} \
${ACLOCAL_ARGS})
Rework the run-autotools target into a series of sub-targets, the order of which can now be overriden. PR: 86309 (slightly reworked) Submitted by: thierry
2005-11-19 00:21:49 +01:00
. else
@${DO_NADA}
Add USE_ACLOCAL_VER= (automake-version), another entry point into using the various GNU autotools, running "aclocal" at configuration time, prior to any other tools. This should allow a number of ports Makefiles to be cleaned up with respect to their explicit calling of ${ACLOCAL} PR: 41945 (reworked for current reality) Submitted by: Bruce M Simpson <bms@spc.org>
2005-06-16 23:52:56 +02:00
. endif
Rework the run-autotools target into a series of sub-targets, the order of which can now be overriden. PR: 86309 (slightly reworked) Submitted by: thierry
2005-11-19 00:21:49 +01:00
.endif
.if !target(run-autotools-automake)
run-autotools-automake:
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. if defined(AUTOTOOL_automake)
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
@(cd ${CONFIGURE_WRKSRC} && ${SETENV} ${AUTOTOOLS_ENV} ${AUTOMAKE} \
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
${AUTOMAKE_ARGS})
Rework the run-autotools target into a series of sub-targets, the order of which can now be overriden. PR: 86309 (slightly reworked) Submitted by: thierry
2005-11-19 00:21:49 +01:00
. else
@${DO_NADA}
Autotools cleanup. Remove autoconf257 (259), automake17 (18), and libtool14 (13/15). PR: 67768 Submitted by: ade Approved by: 4-exp bento runs (thanks, kris!)
2004-07-01 19:06:41 +02:00
. endif
Rework the run-autotools target into a series of sub-targets, the order of which can now be overriden. PR: 86309 (slightly reworked) Submitted by: thierry
2005-11-19 00:21:49 +01:00
.endif
.if !target(run-autotools-autoconf)
run-autotools-autoconf:
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. if defined(AUTOTOOL_autoconf)
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
@(cd ${CONFIGURE_WRKSRC} && ${SETENV} ${AUTOTOOLS_ENV} ${AUTOCONF} \
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
${AUTOCONF_ARGS})
Rework the run-autotools target into a series of sub-targets, the order of which can now be overriden. PR: 86309 (slightly reworked) Submitted by: thierry
2005-11-19 00:21:49 +01:00
. else
@${DO_NADA}
Autotools cleanup. Remove autoconf257 (259), automake17 (18), and libtool14 (13/15). PR: 67768 Submitted by: ade Approved by: 4-exp bento runs (thanks, kris!)
2004-07-01 19:06:41 +02:00
. endif
Rework the run-autotools target into a series of sub-targets, the order of which can now be overriden. PR: 86309 (slightly reworked) Submitted by: thierry
2005-11-19 00:21:49 +01:00
.endif
.if !target(run-autotools-autoheader)
run-autotools-autoheader:
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. if defined(AUTOTOOL_autoheader)
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
@(cd ${CONFIGURE_WRKSRC} && ${SETENV} ${AUTOTOOLS_ENV} ${AUTOHEADER} \
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
${AUTOHEADER_ARGS})
Rework the run-autotools target into a series of sub-targets, the order of which can now be overriden. PR: 86309 (slightly reworked) Submitted by: thierry
2005-11-19 00:21:49 +01:00
. else
@${DO_NADA}
Autotools cleanup. Remove autoconf257 (259), automake17 (18), and libtool14 (13/15). PR: 67768 Submitted by: ade Approved by: 4-exp bento runs (thanks, kris!)
2004-07-01 19:06:41 +02:00
. endif
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
.endif
Over the past few weeks, we have been testing the next incarnation of ports/Mk/bsd.autotools.mk on the road to bringing at least some semblance of sanity back to this corner of the ports collection. By far and away the easiest way to see the changes will be to view the new file once committed, but here is a summary of the changes: 1. USE_LIBTOOL, USE_AUTOCONF, USE_AUTOHEADER, USE_AUTOMAKE have been fully deprecated. Ports attempting to use these variables after the commit will error out, and most obviously break INDEX generation, with a helpful error message. Instead, ports must now specifically choose the version of any of these tools that they need with the corresponding USE_*_VER variables. Note that these variables understand any and all versions of autotools ports in the tree, there is no longer a need to have specific version numbers hardcoded in the infrastructure of bsd.autotools.mk (as there is now). In particular, this will immediately open up automake18 and autoconf259 for general use and beating. 2. Similarly for WANT_LIBTOOL, WANT_AUTOCONF, and WANT_AUTOMAKE. Again, these have been fully deprecated, and the equivalent WANT_*_VER versions should be used. In order to preserve existing behavior for these variables, please note the 20040314 entry in ports/CHANGES for the appropriate version numbers to use for any ports in the GNATS queue. Both WANT_* and USE_* bring in the relevant tool as a build dependency, and set up a reasonably large number of variables pointing to the right programs to be using in the port. The only difference at the moment, is that USE_* will run an extra autotools-related configuration step, whereas WANT_* merely requests the environment. 3. The helper knob USE_LIBLTDL has been added which currently simply adds a LIB dependency on the libltdl port. 4. Three new variables have been introduced, WANT_{LIBTOOL,AUTOCONF,AUTOMAKE}_RUN=yes. These variables will do nothing by themselves (a Work-In-Progress), but if the appropriate autotool version is defined (either through WANT_*_VER or USE_*_VER), this will add the relevant dependency to RUN_DEPENDS. Steps 3 and 4 now essentially negate the need for any kind of direct dependency within a non-autotools port Makefile on devel/autoconf*, devel/automake*, devel/libtool*, and devel/libltdl. PR: 66037 Reviewed by: 4-exp bento cluster
2004-06-04 19:27:29 +02:00
# patch-autotools
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
#
# Special target to automatically make libtool using ports use the
# libtool port. See above for default values of LIBTOOLFILES.
Rework the run-autotools target into a series of sub-targets, the order of which can now be overriden. PR: 86309 (slightly reworked) Submitted by: thierry
2005-11-19 00:21:49 +01:00
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
.if !target(patch-autotools)
Switch to <target>:: convention for both patch-autotools and run-autotools, to allow for easier overriding of these targets by port Makefiles, if they need to.
2005-11-19 07:02:20 +01:00
patch-autotools::
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. if defined(AUTOTOOL_libtool_inc)
Autotools cleanup. Remove autoconf257 (259), automake17 (18), and libtool14 (13/15). PR: 67768 Submitted by: ade Approved by: 4-exp bento runs (thanks, kris!)
2004-07-01 19:06:41 +02:00
@(cd ${PATCH_WRKSRC}; \
for file in ${LIBTOOLFILES}; do \
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
${CP} $$file $$file.tmp; \
Autotools cleanup. Remove autoconf257 (259), automake17 (18), and libtool14 (13/15). PR: 67768 Submitted by: ade Approved by: 4-exp bento runs (thanks, kris!)
2004-07-01 19:06:41 +02:00
${SED} -e "s^\$$ac_aux_dir/ltconfig^${LTCONFIG}^g" \
-e "/^ltmain=/!s^\$$ac_aux_dir/ltmain.sh^${LIBTOOLFLAGS} ${LTMAIN}^g" \
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
$$file.tmp > $$file; \
Autotools cleanup. Remove autoconf257 (259), automake17 (18), and libtool14 (13/15). PR: 67768 Submitted by: ade Approved by: 4-exp bento runs (thanks, kris!)
2004-07-01 19:06:41 +02:00
${RM} $$file.tmp; \
done);
Install the new version of bsd.autotools.mk with support for the USE_AUTOTOOLS stanza. Full backwards compatibility with the current USE/WANT variables has been maintained via a number of shims which are set to expire on January 1st, 2006. Please do *not* start using USE_AUTOTOOLS in port Makefiles until after 6.0-RELEASE has gone out the door. Once that has happened, I will implement a tree-wide conversion process before 5.5-RELEASE, at which points ports will be free to use the new mechanisms. This change has been extensively locally tested with various large consumers of autotools building with no ill-effects notice. However, there may well be edge cases that need to be taken care of. After discussion with various members of portmgr, it was agreed that this commit could go ahead without an -exp run, but that does not, in my mind, constitute full approval. The responsibility for any breakages caused by this commit are mine, and mine alone. Please do file PRs, or mail me directly, if breakage is noticed, and I will endeavor to fix immediately. PR: 82462
2005-07-01 19:04:53 +02:00
. elif defined(AUTOTOOL_libtool)
Apply a big libtool patch to allow porters to use the libtool installed by the libtoolX ports instead of the one included with each port. Ports that set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of the included version. To restore previous behavior, use the new macro, USE_INC_LIBTOOL_VER. Both macros accept the same argument: a libtool version. For example, to use the ports version of libtool-1.5, add the following to your Makefile: USE_LIBTOOL_VER= 15 To use the included version of libtool with extra hacks provided by libtool-1.5, add the following to your Makefile: USE_INC_LIBTOOL_VER= 15 With this change, ports that had to add additional libtool hacks to prevent .la files from being installed or to fix certain threading issues can now delete those hacks (after appropriate testing, of course). PR: 63944 Based on work by:eik and marcus Approved by: ade (autotools maintainer) Tested by: kris on pointyhat Bound to be hidden problems: You bet
2004-07-09 19:43:11 +02:00
@(cd ${PATCH_WRKSRC}; \
for file in ${LIBTOOLFILES}; do \
${CP} $$file $$file.tmp; \
${SED} -e "s^\$$ac_aux_dir/ltconfig^${LTCONFIG}^g" \
-e "/^ltmain=/!s^\$$ac_aux_dir/ltmain.sh^${LIBTOOLFLAGS} ${LTMAIN}^g" \
-e '/^LIBTOOL=/s^\$$(top_builddir)/libtool^${LIBTOOL}^g' \
$$file.tmp > $$file; \
${RM} $$file.tmp; \
done);
Autotools cleanup. Remove autoconf257 (259), automake17 (18), and libtool14 (13/15). PR: 67768 Submitted by: ade Approved by: 4-exp bento runs (thanks, kris!)
2004-07-01 19:06:41 +02:00
. else
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
@${DO_NADA}
Autotools cleanup. Remove autoconf257 (259), automake17 (18), and libtool14 (13/15). PR: 67768 Submitted by: ade Approved by: 4-exp bento runs (thanks, kris!)
2004-07-01 19:06:41 +02:00
. endif
Introduce bsd.autotools.mk to the world, ripped from bsd.port.mk This is essentially a null-commit, with the one exception that the "patch-libtool" target is now called "patch-autotools" for consistency with "run-autotools". Many thanks to kris for testing on the 4-exp bento cluster Approved by: portmgr (kris) Verified by: bento 4-exp
2004-04-19 03:37:12 +02:00
.endif
Reference in a new issue Copy permalink