Frederic Bouvier wrote: > Melchior FRANZ wrote: > > Why the #ifdef? Is there a reasonable case where CONFIG_H is *not* > > available? > > It has always been the practice to enclose #include <config.h> by > #ifdef HAVE_CONFIG_H from the beginning of autoconf/automake.
That's not really an answer to the question: do we or will we ever do a build where there is no config.h? Can such a build work even if we tried it? Based on your recent checking, the answer clearly seems to be no. Just drop the #ifdefs. They're needless complexity, and using them simply because "it's always been done that way" is bad software engineering. Andy ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
