This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: In future, to replace autotools by cmake like KDE4 did?
- From: Jakub Narebski <jnareb at gmail dot com>
- To: "J.C. Pizarro" <jcpiza at gmail dot com>
- Cc: gcc at gcc dot gnu dot org, git at vger dot kernel dot org, "David Miller" <davem at davemloft dot net>, "Daniel Berlin" <dberlin at dberlin dot org>, "Ismail Donmez" <ismail at pardus dot org dot tr>
- Date: Fri, 07 Dec 2007 04:14:42 -0800 (PST)
- Subject: Re: In future, to replace autotools by cmake like KDE4 did?
- References: <998d0e4a0712061810k18e6388jde9d7bc5bd006b57@mail.gmail.com>
"J.C. Pizarro" <jcpiza@gmail.com> writes:
> The autotools ( automake + libtool + autoconf + ... ) generate many big
> files that they have been slowing the building's computation and growing
> enormously their cvs/svn/git/hg repositories because of generated files.
[cut]
And this is relevant for this mailing list exactly how? From the whole
autotools package git uses only autoconf, and only as an optional part
to configure only Makefile configuration variables.
Generated files should not be put into version control, unless it is
for convenience only in separate branch like HTML and manpage versions
of git documentation are in 'html and 'man' branches, respectively.
The same could be done with ./configure script.
Although there was some talk about whether giw should use autotools,
or perhaps CMake, or handmade ./configure script like MPlayer IIRC,
instead of its own handmade Makefile...
--
Jakub Narebski
ShadeHawk on #git