All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: "J.C. Pizarro" <jcpiza@gmail.com>
Cc: 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: Re: In future, to replace autotools by cmake like KDE4 did?
Date: Fri, 07 Dec 2007 04:14:42 -0800 (PST)	[thread overview]
Message-ID: <m3lk86u2fq.fsf@roke.D-201> (raw)
In-Reply-To: <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

  parent reply	other threads:[~2007-12-07 12:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07  2:10 In future, to replace autotools by cmake like KDE4 did? J.C. Pizarro
2007-12-07  7:56 ` Marcel Holtmann
2007-12-07 12:14 ` Jakub Narebski [this message]
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=m3lk86u2fq.fsf@roke.D-201 \
    --to=jnareb@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 \
    --cc=jcpiza@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.