-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've written a treatise on this subject in my autotools book: http://www.freesoftwaremagazine.com/books/agaal/catalog_of_reusable_solutions The first sub-topic is the one you want - "Never expose config.h in a public interface". - --john Ralf Wildenhues wrote: > Hello Václav, > > * Václav Haisman wrote on Wed, Aug 06, 2008 at 09:19:41PM CEST: >> I have this library, it includes autoconf generated config.h in its >> public headers. > > The right approach is to never install config.h, and never let installed > headers include it. If you must, then have a second config header for > which you write the input file yourself (IOW, not generated by > autoheader) and put only nonconflicting defines in there. > > Alternatively, there is a macro in the Autoconf Macro Archive to mangle > config.h to prefix each defined with a package-specific prefix. > > This topic has come up several times on this list, the list archives > should include further useful hints. Any volunteers for writing a FAQ > entry? > > Cheers, > Ralf > > > _______________________________________________ > Autoconf mailing list > Autoconf@xxxxxxx > http://lists.gnu.org/mailman/listinfo/autoconf > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkiaGEAACgkQdcgqmRY/OH9QBACfXimwYAETVkBT30snp29VhVS6 pAEAn3+k2zzezppE1q64iO8cKEOESgEu =HTkN -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
