From: E R <pc88mxer@gmail.com>
To: git@vger.kernel.org
Subject: integrating make and git
Date: Wed, 15 Apr 2009 10:19:31 -0500 [thread overview]
Message-ID: <3a69fa7c0904150819x7598dea5ic43bf0991c35ae45@mail.gmail.com> (raw)
I have an idea about integrating make with git, and I'm wondering if
it is a reasonable thing to do.
First of all, I am under the impression that git can quickly compute a
hash of a directory and its contents. Is that correct?
If so, suppose you using git to manage revision control of a project
which has some components like 'lib1', 'lib2', etc. Typically you
would perform something like: make clean; make all and 'make all'
would perform 'make lib1' and 'make lib2'. When checking out a
different revision of the project you would have to perform another
'make clean' before 'make all' since you aren't sure of what's changed
and the timestamps of the derived files will be more recent than the
timestamps of the source files.
Now suppose that making 'lib1' only depends on the source code in a
certain directory. The idea is to associate the hash of the source
directory for lib1 with its the derived files. Make can check this to
determine if the component really needs to be rebuilt. Then as you
move around in the repository you can avoid rebuilding components that
haven't changed.
Good, bad, ugly?
next reply other threads:[~2009-04-15 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 15:19 E R [this message]
2009-04-15 15:41 ` integrating make and git 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
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=3a69fa7c0904150819x7598dea5ic43bf0991c35ae45@mail.gmail.com \
--to=pc88mxer@gmail.com \
--cc=git@vger.kernel.org \
/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).