Re: [Mingw-cross-env-list] guile

[Tony Theodore]

On 16 April 2010 09:07, Volker Grabsch <address@hidden> wrote:
> Tony Theodore <address@hidden> schrieb:
>> On 15 April 2010 16:23, Volker Grabsch <address@hidden> wrote:
>> > Tony Theodore <address@hidden> schrieb:
>> >> The attached diff removes the autotools trigger by leaving
>> >> *configure.in unpatched.
>> >
>> > Thanks for the patch. I included it:
>> >
>> > http://hg.savannah.gnu.org/hgweb/mingw-cross-env/rev/67c75b116389
>> >
>> > The original idea of changing the configure.in scripts was to provide
>> > a "clean" patch in addition to the hacks directly into the configure
>> > scripts.
>>
>> I'm slowly coming to understand the autotools system, and thought that
>> it was either/or. Patch configure for on-the-fly mingw-cross-env
>> changes, or patch configure.in file for changes upstream. I see from
>> the below that configure.ac is the primary input file, not
>> configure.in.
>
> Don't confuse this. "configure.ac" and "configure.in" are exactly the
> same stuff, i.e. the input file for Autoconf. In ancient versions of
> Autoconf this file was named "configure.in", which is still supported
> for compatibility reasons. But nowadays, one should instead name this
> file "configure.ac", which is a much better name for that file.
>
> Starting with 1.9.x, the Guile project followed that new naming scheme,
> so my changes to "configure.in" are exactly the same as for
> "configure.ac", except that some stuff had been moved into separate
> macros in acinclude.m4, but that's a different story.
>
> For more information on that topic, you might want to take a look
> at the ASCII drawing in the Autoconf manual:
>
> http://www.gnu.org/software/autoconf/manual/html_node/Making-configure-Scripts.html#Making-configure-Scripts

Thanks, that's exactly what I was looking for, I don't know why I
hadn't seen it before.

Tony