[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Why conditionally include config.h?
|
From: |
Kip Warner |
|
Subject: |
Why conditionally include config.h? |
|
Date: |
Thu, 13 Sep 2012 16:22:58 -0700 |
Hey list,
Why do many autoconfiscated projects bracket inclusion of the generated
config.h with #if HAVE_CONFIG_H / #endif. Assuming the build
environment was configured, why shouldn't the source just always
unconditionally include config.h? I mean if it isn't there, typically
that means the user didn't configure first which ought to be an error
anyways, no?
--
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