Frank A. Uepping wrote:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^With AC_DEFINE I can define cpp definitions. Is that legal/supposed-to to access the underlying var in configure.ac? Same for AC_SUBST.
E.g.:
## configure.ac
AC_INIT([foo], [1.0]) ## AC_DEFINE: PACKAGE_TARNAME/VERSION...
AM_INIT_AUTOMAKE([$PACKAGE_TARNAME], [$PACKAGE_VERSION])
## eof configure.ac
BTW: Is the version of AC_INIT meant to be the package version or that of configure.ac?
(I am wondering that AM_INIT_AUTOMAKE doesn't use PACKAGE_* by default.)
me too. Even more bad here, some macros require literals instead of varnames which is definitly SEVERELY MISGUIDED, IMNSHO.
-- guido http://AC-Archive.sf.net GCS/E/S/P C++/++++$ ULHS L++w- N++@ d(+-) s+a- r+@>+++ y++ 5++X-
