[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_CONFIG_HEADERS and autoheader
From: |
Stepan Kasal |
Subject: |
Re: AC_CONFIG_HEADERS and autoheader |
Date: |
Tue, 5 Dec 2006 20:44:59 +0100 |
User-agent: |
Mutt/1.4.2.1i |
Hello,
On Tue, Dec 05, 2006 at 10:17:57AM -0800, Paul Eggert wrote:
> Patrick Welche <address@hidden> writes:
> > Is that AC_CONFIG_HEADERS syntax simply not allowed? (missing file name)
>
> The documentation doesn't seem to allow it.
>
> But also, the documentation seems to say that you can have as many files
> as you like, not just 3. [...]
Indeed, you can have any number of input files for AC_CONFIG_HEADERS,
as for AC_CONFIG_FILES.
So you can have
AC_CONFIG_HEADERS([defines.h:def1.h:def2.h:def3.h:def4.h])
And if this is the first config header in the configure.ac, which of
the input files should be picked by autoheader?
I do not see a better answer than what the current implementation
has: autoheader picks the first one.
Consequently, I think Patrick's patch should not be accepted.
But I think we should improve the documentation; most importantly, we
should point out that AH_BOTTOM is usually better that multiple input
files.
Attached please find a first approximation of the documentation
patch. Wdyt?
Have a nice day,
Stepan Kasal
autoconf-20061205-doc-ah.patch
Description: Text document