[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What to do about config.h, etc...

From: Rob Browning
Subject: Re: What to do about config.h, etc...
Date: Tue, 04 Mar 2003 18:55:13 -0600
User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu)

Andreas Rottmann <address@hidden> writes:

> If you take a look at how other libraries, (e.g. GLib) do this, you'll
> see that most of them that need a public-installed, platform-specific
> header, use autoconf's AC_CONFIG_COMMANDS macro to generate that
> header by a shell script run at configure time.

My initial trial code seems reasonably promising, but this approach
does introduce the limitation that (without special precautions) we
can't use AC_DEFINE(GUILE_DEBUG ...) *and* expect to use GUILE_DEBUG
in our public header -- the two definitions, the one in config.h and
the one in libguile/scmconfig.h, would conflict.

The solution I'm leaning toward is to just remove the AC_DEFINEs for
any values we want to make public.  That's probably OK since we have
to duplicate the AC_DEFINE information in the AC_CONFIG_COMMANDS when
generating scmconfig.h anyway.  However, this does mean that if there
are any symbols that automatically AC_DEFINEs that we
also want to make public, we'll have to choose another name for the
public incarnation.

Rob Browning
rlb,, and
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4

reply via email to

[Prev in Thread] Current Thread [Next in Thread]