autoconf
[Top][All Lists]
Advanced

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

Re: Conditional AH_VERBATIM


From: Stepan Kasal
Subject: Re: Conditional AH_VERBATIM
Date: Sun, 8 Jan 2006 15:27:25 +0100
User-agent: Mutt/1.4.1i

Hello,

On Thu, Jan 05, 2006 at 06:58:47PM -0700, Brian wrote:
> I'd like to conditionally insert
> 
> > #ifndef TOKEN
> > # define TOKEN
> > #endif
> 
> but autoheader just snags everything that uses AH_VERBATIM.

back to the roots:
1) on the developer's system, autoheader and autoconf are run to create
config.h.in and configure.  These are packed in a tarball.
2) on the user's system, the distributed shell script `configure' sniffs
around and outputs its findings by ``filling in form''--creating config.h
from the template config.h.in.  (Neither autoheader nor autoconf has to
be installed there.)

Yes, if you build from CVS using a bootstrap script which does both
steps (such as autogen.sh scripts in Gnome), it's easy to forget about
the above rules.
But I'm afraid you would have to speand much time if you decided to
change them.

With this in mind, what did you meant by "conditionally"?

If you wanted to evaluate the condition on the developer's machine, at
the time when autoconf and autoheader runs, then things should work.
If you use m4_if and properly quotes its arguments, autoheader won't
snag occurences of AH_VERBATIM which are not expanded.

If you wanted to influence the config.h.in at the time when
./configure runs, that's simply not possible.  Perhaps you could use
AC_SUBST and AC_CONFIG_FILES to edit a header which will then get
#included from config.h or another header.  But I'd have to know what
you are trying to achieve to be able to help you to find a way.

Have a nice day,
        Stepan Kasal




reply via email to

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