On Tue, 2004-11-02 at 16:15 +0000, Martyn Russell wrote: > On Mon, 2004-11-01 at 14:22 -0700, Michael L Torrie wrote: > > On Mon, 2004-11-01 at 21:10 +0000, Tor Lillqvist wrote: > > > > > That is presumably quite unnecesary. It's also counter-productive, as > > > it might make people think that GTK's config.h file is supposed to be > > > available when compiling software that just uses GTK. Which is not the > > > case at all. If some developer package of GTK (or GLib, Pango, etc) > > > includes the config.h file, that's an error. > > > > Is it incorrect to put #ifdef CONFIG_H around the #include <config.h>? > > (Or whatever autoconf sets as a flag these days.) > > I thought it was: > > #ifdef HAVE_CONFIG_H > #include <config.h> > #endif I don't know who started it propagating this bit of code, but it should be stopped. :-) Projects have config.h files, or they don't. They don't optionally have config.h files. Regards, Owen
Attachment:
signature.asc
Description: This is a digitally signed message part