[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why conditionally include config.h?
From: |
Kip Warner |
Subject: |
Re: Why conditionally include config.h? |
Date: |
Sat, 15 Sep 2012 17:24:02 -0700 |
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
signature.asc
Description: This is a digitally signed message part
Re: Why conditionally include config.h?, Kip Warner, 2012/09/15
Re: Why conditionally include config.h?, Bob Friesenhahn, 2012/09/13