[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
PACKAGE vs PACKAGE_TARNAME
From: |
infirit |
Subject: |
PACKAGE vs PACKAGE_TARNAME |
Date: |
Sun, 2 Feb 2014 03:25:35 +0100 |
Hi,
So for a project we wanted to make the tarball different from from the
package name. So we updated AC_INIT and added the tarname and indeed
now the tarball generated changes.
However, we noticed that now the $PACKAGE variable is also changed to
what we set as tarname. Which then caused files being installed in the
wrong place as now $(pkgdatadir) changed as well.
As an example, we changed
AC_INIT([this_is_package], [0.0.1], [http://someurl/])
to
AC_INIT([this_is_package], [0.0.1], [http://someurl/],
[this_is_package_tarname])
I tested this with a small configure.ac and empty Makefile.am. The
example is below.
--
AC_INIT([this_is_package], [0.0.1],[http://someurl/],[this_is_package_tarname])
AM_INIT_AUTOMAKE([1.9 foreign dist-xz no-dist-gzip])
AC_OUTPUT
AC_CONFIG_FILES([Makefile])
echo ${PACKAGE}
echo ${PACKAGE_TARNAME}
--
I put in some echo's at the end of the configure.ac and indeed the
variables $PACKAGE and $PACKAGE_TARNAME *both* change when adding the
tarname to AC_INIT.
Is this a bug in autoconf or are we missing something?
I am not subscribed so please cc me on replies.
Thx
~infirit
- PACKAGE vs PACKAGE_TARNAME,
infirit <=