autoconf-patches
[Top][All Lists]
Advanced

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

Re: Documentation chapter: The GNU build system


From: Steven G. Johnson
Subject: Re: Documentation chapter: The GNU build system
Date: Tue, 24 Apr 2001 10:58:02 -0400 (EDT)

On 24 Apr 2001, Akim Demaille wrote:
> +provided by @code{configure}.  Into this mess steps @strong{Automake}.
> 
> strong seems a bit strong precisely.  How about dfn and a cindex?

Good point, okay (I forgot about dfn).

> +The resulting @code{Makefile.in} (~400 lines) automatically supports all
> 
> Does ~ really come out as a tilde and not a nonbreaking space?

It comes out as a tilde, no worries.

> address@hidden, if not @file{/usr/local}).  Automake requires that
> address@hidden be installed on the developer's machine in order to generate
> 
> As noted by Alexandre this will no longer be true, so I would not
> include it.

See my previous email for a rephrasing.  I think it's important to point
out that some versions of Automake (maybe in the future, too) may require
special tools on the developer's machine (e.g. Automake and Autoconf are
required in any case), but that 'make dist' produces something portable.
Not only is this true of the current Automake (which will hang around for
a while before the CVS version is released and becomes prevalent), but
this also seems to be a common misunderstanding about Automake.  (I've
heard it several times, anyway, as a reason for avoiding Automake in
large projects, e.g. MPICH.)

> That's a great piece of work, thanks!  Just one note: could you fill
> the menus?  Something like

Okay, how about:

* Automake::                    Escaping Makefile hell
* Libtool::                     Portable shared libraries
* Pointers::                    More info on the GNU build system

Steven




reply via email to

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