On Tue, 13 May 2008, aaragon wrote:
Could you please expand on this? I don't really understand what you're
talking about. The config.h file has just a bunch of #define statements and
there is no namespace (and I don't think that hardcoding one is the way
out).
I use this in configure.ac:
AC_CONFIG_HEADERS([magick/magick_config.h magick/magick_config_api.h])
with magick/magick_config.h being used to build the software, and
magick/magick_config_api.h installed as magick/magick_config.h at
installation time. The magick/magick_config_api.h.in template file
needs to be hand-maintained and contains only what is required to
satisfy the library headers.
It seems that I (somewhat) lied about the define naming. As long as
the number of definitions required is small, you can provide your own
with a useful prefix (e.g. "ARAGON_FOO") so that they won't be
confused with some other package's definitions.
Bob
======================================
Bob Friesenhahn
bfriesen@xxxxxxxxxxxxxxxxxxx, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
