From: "J.C. Pizarro" <jcpiza@gmail.com>
To: gcc@gcc.gnu.org, git@vger.kernel.org,
"David Miller" <davem@davemloft.net>,
"Daniel Berlin" <dberlin@dberlin.org>,
"Ismail Donmez" <ismail@pardus.org.tr>
Subject: In future, to replace autotools by cmake like KDE4 did?
Date: Fri, 7 Dec 2007 03:10:36 +0100 [thread overview]
Message-ID: <998d0e4a0712061810k18e6388jde9d7bc5bd006b57@mail.gmail.com> (raw)
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.
* less errors/crashes when it's configuring.
* can be improved the cmake's sources for better performance's gain.
* good and long maintainance life.
I hope if the files for cmake+make can be well integrated in GCC 4.4
J.C.Pizarro
next reply other threads:[~2007-12-07 2:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 2:10 J.C. Pizarro [this message]
2007-12-07 7:56 ` In future, to replace autotools by cmake like KDE4 did? Marcel Holtmann
2007-12-07 12:14 ` Jakub Narebski
2007-12-07 12:44 ` Andreas Ericsson
2007-12-07 13:56 ` Jakub Narebski
2007-12-07 14:42 ` J.C. Pizarro
2007-12-07 16:10 ` Marco Costalba
2007-12-10 20:23 ` Jan Hudec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=998d0e4a0712061810k18e6388jde9d7bc5bd006b57@mail.gmail.com \
--to=jcpiza@gmail.com \
--cc=davem@davemloft.net \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=git@vger.kernel.org \
--cc=ismail@pardus.org.tr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).