Re: Why conditionally include config.h?

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

 



On Fri, 2012-09-14 at 02:58 +0300, Marko Lindqvist wrote:
>  I've seen some packages where same sources are used with multiple
> build systems (typically autotools in more unixy systems and visual
> studio project files on Windows) and it's actually needed to weed out
> "config.h" include when building with system that does not provide it.
> But more often "#ifdef HAVE_CONFIG_H" is just idiom copied from some
> other project.
> 
>  For example, in our freeciv project, this would need cleanup. It used
> to be possible to build without autotools and fc_config.h (for systems
> lacking autotools support those ancient times), and thus #ifdefs are
> used. However, if one would try to build without HAVE_CONFIG_H defined
> today, it would go horribly wrong.

Thanks Marco. Very helpful.

-- 
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://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