-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [adding bug-automake] According to Andrew W. Nosenko on 3/3/2009 4:12 AM: > Possible stupid question, but could someone explain, why required > macros (at least such my impression from reading the Autoconf info) > like AT_PACKAGE_NAME, AT_PACKAGE_VERSION, AT_PACKAGE_BUGREPORT are > required to be defined by user while they can be defaulted from the > AC_PACKAGE_NAME, AC_PACKAGE_VERSION, AC_PACKAGE_BUGREPORT, and so > on?.. Because the autotest language was designed to be run separately from autoconf, if you so desire. Even though most users (all except for the autoconf testsuite?) tend to also use autoconf. > > Or I'm not required to define these macros in the package.m4 indeed, > and, possible, to generate package.m4 at all? My tryings show that > required, but may be I missed something... The autoconf documentation gives a formula for writing a Makefile snippet that will create the necessary package.m4. Also, there is little automake support for autotest at the moment, but if someone were to propose an automake extension that takes care of building package.m4 and all the other Makefile snippets recommended in the autoconf manual, I'm sure it would be appreciated. - -- 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 iEYEARECAAYFAkmtKgMACgkQ84KuGfSFAYB8+wCeJBaXNPbmWQBOyFOCFr1GkSCT 4vsAoKnUmJghjZQ0ya670GCbYZKWKR7u =1o7O -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
