autoconf-patches
[Top][All Lists]
Advanced

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

Re: Explanation in autoconf manual


From: Eric Blake
Subject: Re: Explanation in autoconf manual
Date: Thu, 25 Feb 2010 15:51:47 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666

[Visiting another old thread]

According to santilistas on 8/9/2009 4:31 AM:
> In chapter 3, the diagram showing files for configuring and distributing
> has a line like this:
>
> Makefile.in ----------------------------------------> Makefile.in
>
> Is this ok?

According to Ralf Wildenhues on 8/10/2009 1:32 PM:
> * Philip Herron wrote on Mon, Aug 10, 2009 at 02:08:41AM CEST:
>> The pipeline is this:
>>
>>                       *Automake                       *Autoconf
>> Makefile.am  -------------> Makefile.in -> configure.ac -> Makefile
> 
> Nope.  While automake turns *.am files into *.in files for each * listed
> in an AC_CONFIG_FILES macro in configure.ac, the script that turns *.in
> files into * files is named config.status, and is generated and invoked
> by the configure script.  Confusing, eh?  ;-)

The autoconf manual already has a number of places that call out behavior
both with and without automake.  So, I think the best thing to do here is
try and expand the diagram to show that automake is optional, as well as
how it fits in when used.  Here's what I'm thinking of; any ideas for
improvements?

santalistas, do you have a preferred name to be listed as in THANKS?
Right now, it only lists your email address with "santilĂ­n".

-- 
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden

Attachment: autoconf.patch255
Description: Text document

Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

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