[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
How to maintain compatibility with Automake.
From: |
Peter Rosin |
Subject: |
How to maintain compatibility with Automake. |
Date: |
Tue, 10 Aug 2010 10:19:53 +0200 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 |
Hi!
A macro by the name AM_PROG_AR might be on its way into Automake,
and I would like to use it sooner rather than later. But I don't
think it is prudent to require an Automake version which has the
macro. Would something like this be a workable solution in
libtool.m4 (untested, needs adjustments to _LT_CMD_OLD_ARCHIVE
of course)?
m4_ifndef([AM_PROG_AR],
############################################################
# NOTE: A macro with the same interface as this has been #
# submitted for inclusion into GNU Automake as #
# AM_PROG_AR. When we require an Automake version which #
# has this macro we should remove this macro from here #
# and use the Automake macro unconditionally. #
############################################################
[
m4_defun([AM_PROG_AR],
[AC_CHECK_TOOLS(AR, [ar], false)
: ${AR=ar}
AC_SUBST([AR])dnl
])# AM_PROG_AR
])
Or how are situations like this generally handled?
Cheers,
Peter
- How to maintain compatibility with Automake.,
Peter Rosin <=