[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Automake 1.12.0b test release
From: |
Bob Friesenhahn |
Subject: |
Re: Automake 1.12.0b test release |
Date: |
Sun, 20 May 2012 17:14:41 -0500 (CDT) |
User-agent: |
Alpine 2.01 (GSO 1266 2009-07-14) |
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 version and tarball name are stale and reflect
the last time autoconf was executed.
I added a Makefile.am rule to encourage autoconf to be run to update
configure. This was not sufficient. In fact, I find that when I run
'autoconf' manually, the values used are cached values and used
perpetually rather than the new values returned by my scripts. This
cache caused considerable confusion for me while I was developing my
version script because the defective cached value was used until I
removed the autom4te.cache directory or executed 'autoconf --force'.
What is necessary in order to cause "dynamic" AC_INIT arguments to
actually work? Is there a way to convince Automake to invoke autoconf
with the --force option?
Thanks,
Bob
--
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/