[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AC_CONFIG_HEADERS and autoheader
From: |
Patrick Welche |
Subject: |
Re: AC_CONFIG_HEADERS and autoheader |
Date: |
Wed, 6 Dec 2006 12:13:47 +0000 |
User-agent: |
Mutt/1.5.13 (2006-11-21) |
On Tue, Dec 05, 2006 at 08:44:59PM +0100, Stepan Kasal wrote:
> 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.
Right: and how do you tell which to prepend and which to append?!
As you say the documentation isn't clear..
> 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.
Sounds good!
Patrick