On Mon, 2004-09-13 at 17:20, Bob Friesenhahn wrote: > The fact of the matter is that some/many libraries have header files > which are OS/CPU/compiler dependent and there has to be a way to > record/work-around these dependencies so that the library headers work > right. This way is commonly known as 'config.h'. Yes, but this is not what current autoconf's autoheaders are about. > As for myself, I find that installing a trimmed-down configuration > header which only includes the definitions required for the headers to > work correctly is the best choice. I have found myself in the same boat, but, and this might be a surprize to you: Such config-headers in most cases boil down to very few defines, which very easily can be encoded into very simple configure-script fragments. Ralf _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
