[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: autoconf 2.61: AC_DEFINE variable with parenthesis
From: |
Stepan Kasal |
Subject: |
Re: autoconf 2.61: AC_DEFINE variable with parenthesis |
Date: |
Tue, 19 Dec 2006 12:40:33 +0100 |
User-agent: |
Mutt/1.4.2.1i |
Hello,
On Tue, Dec 19, 2006 at 01:15:17PM +0200, Andrey Simonenko wrote:
> For example macro with arguments, depending on configure tests
> its value can be different. In config.h.in there can be "#undef DEF"
> (written by hands or generated by autoheader) and configure can
> change this line to "#define DEF(x) somevalue", where "somevalue"
> can or can't use x.
yes, but it seems that in practice it is nicer to encode the finding
into several defined values (HAVE_FOO, HAVE_BROKEN_THAT, ...), and
then define the parametrized macro in a separate hader file:
#ifdef HAVE_FOO
# define DEF(x) expression1
#elif HAVE_BROKEN_THAT
# define DEF(x)
#else
# define DEF(x) something else
#endif
as you did when Paul decalred the feature as deprecated.
And I think this is the right way.
So I tend to believe that having macros without parameters in config.h
is enough to transfer the information found out by configure.
Regards,
Stepan
AC_CONFIG_HEADERS regression (was: Re: autoconf 2.61: AC_DEFINE variable with parenthesis), Stepan Kasal, 2006/12/15
Re: autoconf 2.61: AC_DEFINE variable with parenthesis, Paul Eggert, 2006/12/15
Message not available