[Top][All Lists]

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

Re: autoheader failing with multiple source AC_CONFIG_HEADERS

From: Ross Burton
Subject: Re: autoheader failing with multiple source AC_CONFIG_HEADERS
Date: Mon, 18 Jun 2007 12:14:22 +0100

On Fri, 2007-06-15 at 16:24 -0700, Noah Misch wrote:
> > I have created config.h.post, and want
> > autoheader to generate config.h.in.  However, when autoheader runs it
> > creates a file called "config.h.in:config.h.post".
> This is certainly the wrong behavior.  I'm not so sure of how to improve on 
> it,
> besides refusing to generate any header for this.  In your example, a human 
> can
> easily guess that `config.h.in' is the header to be generated.  Other cases 
> will
> be unclear; which header should `autoheader' generate of these?
> AC_CONFIG_HEADERS([config.h:config.1:config.2:config.3:config.4])

How about looking at the input headers for a filename that is the output
header with ".in" appended, just like it does when there is no set of
input headers.  When there is no such file, it should not generate

> For now, you can work around the problem like this:
> 1) Change configure.ac to use `AC_CONFIG_HEADERS([autoconfig.h])'.
> 2) Move `config.h.post' to `config.h' and add `#include <autoconfig.h>' up 
> top.
> If you need defines substituted into the current content of config.h.post,
> you'll need to shuffle things a bit more.

Cunning.  I worked around my problem another way, but this is a good

Ross Burton                                 mail: address@hidden
                                          jabber: address@hidden
                                     www: http://www.burtonini.com./
 PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

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