Re: including autoconf paths in source

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Monty Taylor on 12/20/2008 11:57 AM:
> 
> I'm wondering if it would be worthwhile to add an AC_DEFINE form, like
> AC_DEFINE_EXPANDED, that would fully-expand things before putting them
> in config.h.

No, because that would violate GNU Coding Standards that the user be able
to override $(prefix) at make time and have it affect all the other
variables.  Really, the best solution is to do exactly what we have
already pointed you to - the gnulib module configmake is the ideal example
of how to propagate these variables into source code:
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=modules/configmake;h=5160128;hb=78f5fbf

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAklNx5YACgkQ84KuGfSFAYDZvACePl+/+2T8SlL6U1PrtEepFm94
2SsAmQHoTVZDy87ajRb1ePY95ZyHIEr6
=ty9x
-----END PGP SIGNATURE-----