public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Han-Wen Nienhuys <hanwen@xs4all•nl>
To: Junio C Hamano <junkio@cox•net>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Allow building GIT in a different directory from the source directory
Date: Tue, 12 Dec 2006 12:50:55 +0100	[thread overview]
Message-ID: <457E979F.9060307@xs4all.nl> (raw)
In-Reply-To: <7vbqm9xz8z.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano escreveu:
> Han-Wen Nienhuys <hanwen@xs4all•nl> writes:
> 
>> GIT can now be built in a separate builddirectory. This is done as
>> follows:
>>
>>   mkdir build
>>   cd build
>>   $my_git_dir/configure
>>   make
> 
> Somehow making this depend on the use of configure feels wrong,
> since we tried to keep that config.mak.gen built by configure
> strictly optional.  In other words, I think the result of your
> patch should be buildable with or without ./configure in a
> separate directory if we are going to do this.
> 
> Care to explain why it is too cumbersome to handle without
> ./configure magic?

I already tried to explain in a previous thread on the list. 
See 

  http://article.gmane.org/gmane.comp.version-control.git/33487
  
you can still build git in the same directory as source 
without using autoconf, and plain make.

If you insist, I can create a separate

  setup-builddir.sh

to setup the build directory; according to the principle of least
surprise, it should happen in the configure script though.

I still don't understand the problem with autoconf; there are already
plenty of baroque shell scripts in GIT.  I hate writing m4 macros as
well, but that's not a problem for GIT users (ie. people who compile
GIT).

For them, 

  ./configure ; make ; make check ; make install

is actually the standard way to compile stuff.


-- 

next prev parent reply	other threads:[~2006-12-12 11:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-11 13:56 [PATCH] Allow building GIT in a different directory from the source directory Han-Wen Nienhuys
2006-12-12  9:03 ` Junio C Hamano
2006-12-12 11:50   ` Han-Wen Nienhuys [this message]
2006-12-12 18:55     ` Johannes Schindelin
2006-12-13  9:28       ` Andreas Ericsson
  -- strict thread matches above, loose matches on Subject: below --
2006-12-08 17:15 Han-Wen Nienhuys
2006-12-08 17:44 ` Jakub Narebski
2006-12-08 18:14   ` Han-Wen Nienhuys
2006-12-09  1:16 ` Alex Riesen

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=457E979F.9060307@xs4all.nl \
    --to=hanwen@xs4all$(echo .)nl \
    --cc=git@vger$(echo .)kernel.org \
    --cc=junkio@cox$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox