Re: Installable config.h files

[Guido Draheim]

Do I understand it correctly that one would have to create the 
config.h.in template file manually? Hmmm.

May I put a pointer here to that alternative with a pkg-config.h 
derived from standard config.h? It has served as a good basis for me.
http://www.gnu.org/software/ac-archive/Miscellaneous/ac_create_prefix_config_h.html
The generated pkg-config.h will then be included by a project specific 
(and installable) header file that adds defines with a longer body
based on the features detected during `configure`-time.

Apart from this, I'd like to remind eveyone that the real cause of
config.h being non-installable is the fact that there is no way to have
multiple inclusions of config.h files from different (sub-)projects
since the feature-defs are not ifndef'ed. A lot of redefined-warnings
would come up that would not look nice - and the project seriously
buggy which it wouldn't needfully be. Everything would be a bit
easier if the feature-defs would read:
#ifndef HAVE_SYS_TIME_H
#define HAVE_SYS_TIME_H 1
#endif
but may be there is an intention about the non-ifdef scheme?

cheers,
-- guido                                http://guidod.4t.com
31:GCS/E/S/P C++$++++ ULHS L++w- N++@   d(+-) s+a- y++ 5++X-