This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: In future, to replace autotools by cmake like KDE4 did?

From: Marcel Holtmann <marcel at holtmann dot org>
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, 7 Dec 2007 08:56:47 +0100
Subject: Re: In future, to replace autotools by cmake like KDE4 did?
References: <998d0e4a0712061810k18e6388jde9d7bc5bd006b57@mail.gmail.com>

Hi,

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.
To see below interesting links:
1. http://dot.kde.org/1172083974/
2. http://sam.zoy.org/lectures/20050910-debian/
3. https://lwn.net/Articles/188693/
4. http://en.wikipedia.org/wiki/GNU_Build_Tools
5. http://en.wikipedia.org/wiki/GNU_Automake
The benefits could be:
* +40% faster in the KDE4 building vs KDE 3.5.6.
* elimination of redundant and unnecesary generated files as those
 from autotools.
* smaller cvs/svn/git/hg repositories.

stop spreading this FUD. If you leave the auto-generated files from autotools in the source control repositories, then it is your fault. They are generated files and can always be generated. Hence putting them under revision control makes no sense and so don't do it. And more certain don't complain about it if you did.

Regards

Marcel

References:
- In future, to replace autotools by cmake like KDE4 did?
  - From: J.C. Pizarro

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]