From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: Jeff King <peff@peff.net>,
Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
E R <pc88mxer@gmail.com>,
git@vger.kernel.org
Subject: Re: integrating make and git
Date: Thu, 16 Apr 2009 22:50:39 +1000 [thread overview]
Message-ID: <fcaeb9bf0904160550u1a2911eai7e51ed92e6f6aa31@mail.gmail.com> (raw)
In-Reply-To: <vpq63h42a9y.fsf@bauges.imag.fr>
On Thu, Apr 16, 2009 at 7:55 PM, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
> Jeff King <peff@peff.net> writes:
>
>> But one could probably design a system to replace both ccache and make
>> that relies on git's fast sha-1 reporting to avoid duplicate work. I
>> suspect nobody has bothered because make+ccache is "fast enough" that
>> the added complexity would not be worth it.
>
> AIUI, ClearCase does something similar to that. Call that an immense
> bloatware where everything has to come together, or a nice integration
> of different tools, I never used it, so I don't know (I heard the
> first option more than the second ...).
It does help on really big projects (complete rebuild may take one
day, complete recollect built objects and link them with clearmake
take about one hour). C++-based projects may like it due to long time
compilation.
--
Duy
next prev parent reply other threads:[~2009-04-16 12:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 15:19 integrating make and git E R
2009-04-15 15:41 ` Matthieu Moy
2009-04-15 16:20 ` Daniel Barkalow
2009-04-15 16:47 ` E R
2009-04-15 17:30 ` Robin Rosenberg
2009-04-16 8:26 ` Jeff King
2009-04-16 9:55 ` Matthieu Moy
2009-04-16 12:50 ` Nguyen Thai Ngoc Duy [this message]
2009-04-15 21:01 ` Daniel Barkalow
2009-04-15 21:34 ` John Bito
2009-04-16 3:50 ` Ben Jackson
2009-04-16 8:05 ` David Kågedal
2009-04-17 17:24 ` Dmitry Potapov
2009-04-18 7:03 ` Ealdwulf Wuffinga
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=fcaeb9bf0904160550u1a2911eai7e51ed92e6f6aa31@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=pc88mxer@gmail.com \
--cc=peff@peff.net \
--cc=robin.rosenberg.lists@dewire.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 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).