Question on design of a C++ library w.r.t. config.h contents

[Michael D. Beynon]

I have a C++ library that I use with autotools.  I have a config.h that
gets produced, and is included by BOTH the library c++ files and the
header files.  These header files are also exported for users of the
library.  The problem is if the users also use autotools, the PACKAGE,
VERSION, etc. symbols collide, and the current version of g++3.2
produces many warnings.  I want to fix this somehow.  The library
header files MUST include config.h because I use tests from many C++
ISO conformance test macros and use the results (HAVE_BOOL,
HAVE_DYNAMIC_CAST, etc.), and these must be in library exposed structs
and even in template code.

My question: how can I accomplish this?  I could not use autoheader,
and make the config.h.in myself, but this seems like a maintence
problem if/when I update configure.ac in the future.  I could also
write a post-processor for config.h to wrap some #defines with #ifdef
XXX, and then dont define XXX in the header, but define XXX in the
source files to avoid the extra cpp symbols PACKAGE, VERSION, etc.

Mike.


Suggestions?

__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2