From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Allow building GIT in a different directory from the source directory
Date: Fri, 08 Dec 2006 18:44:03 +0100 [thread overview]
Message-ID: <elc84p$4cs$1@sea.gmane.org> (raw)
In-Reply-To: elc6j2$vej$1@sea.gmane.org
Han-Wen Nienhuys wrote:
> From 105d331aee95c0cf3610ac0d2fd4aa7688bd5211 Mon Sep 17 00:00:00 2001
This line is not needed.
> From: Han-Wen Nienhuys <hanwen@xs4all.nl>
> Date: Fri, 8 Dec 2006 18:07:56 +0100
>
> GIT can now be built in a separate builddirectory. This is done as
> follows:
>
> mkdir build
> cd build
> $my_git_dir/configure
> make
Perhaps we should add this to INSTALL file, or to comments in either
Makefile, or configure.ac?
> In this case, configure creates an empty directory tree based on the
> source directory, and wraps Makefiles from source directory in the
> build directory. The rest of the functionality is delivered with the
> VPATH feature of Make.
>
> To make this work the Makefile should not mention ./ explicitly in
> rules, but rather use $< and $^ to automatically look in the source
> dir too.
>
> perl/Makefile and perl/Makefile.PL need special massaging because perl
> is not VPATH aware.
>
> Signed-off-by: Han-Wen Nienhuys <hanwen@xs4all.nl>
Very nicely written commit message. Good work.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-08 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 17:15 [PATCH] Allow building GIT in a different directory from the source directory Han-Wen Nienhuys
2006-12-08 17:44 ` Jakub Narebski [this message]
2006-12-08 18:14 ` Han-Wen Nienhuys
2006-12-09 1:16 ` Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2006-12-11 13:56 Han-Wen Nienhuys
2006-12-12 9:03 ` Junio C Hamano
2006-12-12 11:50 ` Han-Wen Nienhuys
2006-12-12 18:55 ` Johannes Schindelin
2006-12-13 9:28 ` Andreas Ericsson
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='elc84p$4cs$1@sea.gmane.org' \
--to=jnareb@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).