-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to John Calcote on 4/22/2009 5:09 PM: >> Problem is, how do I do that? I tried to add this macro (and the >> prerequisites) inside aclocal.m4, but it seems aclocal.m4 gets >> autogenerated >> by aclocal whenever autoconf makes the configure script. >> > > If you use Autoconf alone, then aclocal.m4 is the place to put extra > macro definitions. However, when you use it with Automake, then the > aclocal utility gathers macro definitions from multiple locations and > overwrites aclocal.m4 with these various extra sources. In this case, > use acinclude.m4, as that's one of the places that aclocal gathers from > to build the new aclocal.m4 file. Is there anything we can do to the autoconf documentation to make this point more clear? We do want to support both camps of users - those who use just autoconf (and edit aclocal.m4), and those who use automake (who edit acinclude.m4 or dump files in the m4 include directory), and the documentation should make it clear which approach a developer should use based on the tools they are currently using. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----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 iEYEARECAAYFAknv1loACgkQ84KuGfSFAYB0BQCfWl6cEmV5ovmZw3qnCUpSoee4 HoQAn1uzsnxnGBkkrFzztJvT5G5ZagN7 =KACe -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
