On Tue, Aug 14, 2012 at 06:57:02PM -0500, Bob Friesenhahn wrote:
AC_INIT(m4_esyscmd([scripts/pkginfo.sh package_name]),
m4_esyscmd([scripts/pkginfo.sh package_version]),
m4_esyscmd([scripts/pkginfo.sh package_bugreport]))
Unfortunately, the values passed to AC_INIT are cached
Hi Bob, I managed to find your old message about dynamically computing
package versions for Automake and Autoconf. Some initial comments
follows. I'm adding the Autoconf list in CC:, because I believe this
is an Autoconf issue more than an Automake one.
On 05/20/2012 12:59 AM, Bob Friesenhahn
On Wed, 15 Aug 2012, Stefano Lattarini wrote:
AM_INIT_AUTOMAKE($PACKAGE_NAME,${PACKAGE_VERSION}${PACKAGE_VERSION_ADDENDUM},
' ')
The reason is because it avoids needing to edit configure.ac (a really stupid
practice)
I agree with this; with today's DVCS, it's very tempting (and IMHO useful)
The script I intend to use to obtain package information is in the
GraphicsMagick repository and produces information gleaned from a
'version.sh' script which has the smarts to produce some obvious
variable names.
echo `./scripts/pkginfo.sh package_bugreport`
[Re-adding the list, because I think the issue might be of general interest]
On 05/20/2012 12:59 AM, Bob Friesenhahn wrote:
Stefano,
This change will cause significant issues for GraphicsMagick unless there is
a workaround:
- Support for the two- and three-arguments invocation forms of
I got AC_INIT dynamic arguments working except that they don't
actually work. Unlike the previous method that I used (evaluated when
configure is executed), the arguments are only evaluated when autoconf
is executed. This means (for example) that when I type 'make dist'
the generated package
