Re: Solving the config.h nightmare ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 22 Apr 2006, Daniel Reed wrote:

It's almost always a mistake to install generated headers. Distribute an .m4 with your software that [re]performs all of the checks that dependent software will need to make. Install that instead of what is essentially just the cached output of its run (which is what your config.h is, whatever you prefer to call it) so dependent software devlopers can just call OB_PROG_CEYLON in their configure.ac and get their own config.h files (or CPPFLAGS or whatever mechanism they prefer) sanitized.

This is an interesting approach, but dependent software will then be using tests which are possibly out of date as soon as the dependent package is distributed. While possibly solving some problems, the approach creates new ones.

Bob
======================================
Bob Friesenhahn
bfriesen@xxxxxxxxxxxxxxxxxxx, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux