[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: |
Ralf Wildenhues |
Subject: |
Re: autoconf 2.61: AC_DEFINE variable with parenthesis |
Date: |
Tue, 19 Dec 2006 12:47:02 +0100 |
User-agent: |
Mutt/1.5.13 (2006-11-01) |
* Stepan Kasal wrote on Tue, Dec 19, 2006 at 12:40:33PM CET:
> 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:
I disagree. Putting things in two separate files which belong together
isn't "nice and clean" from an application point of view. It's coding
around a restriction that Autoconf imposes upon the user (and has failed
so far to document very explicitly).
Cheers,
Ralf
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