git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henry Qin <root@hq6.me>
To: Junio C Hamano <gitster@pobox.com>, dennis@kaarsemaker.net
Cc: git@vger.kernel.org
Subject: Re: Is it possible to build `git` such that the install directory and the deployment prefix is not the same?
Date: Fri, 27 Nov 2015 23:58:02 -0800	[thread overview]
Message-ID: <CAO8bsPB98QRDRRftHNvLYafB-_EA_sbLMmB5SxxEjY+uRhKKCg@mail.gmail.com> (raw)
In-Reply-To: <xmqqmvty8soc.fsf@gitster.mtv.corp.google.com>

Thanks a lot, Junio and Dennis!

~Henry

On Fri, Nov 27, 2015 at 11:47 PM, Dennis Kaarsemaker
<dennis@kaarsemaker.net> wrote:
> On vr, 2015-11-27 at 23:19 -0800, Henry Qin wrote:
>
>> Is there a way to specify during either configure or make that I want
>> a different path for actual deployment, such as /usr/bin/local, but
>
> There is, using the DESTDIR variable:
>
> make PREFIX=/usr/local
> DESTDIR=$(PWD)/dist make install
> --
> Dennis Kaarsemaker
> www.kaarsemaker.net
>
>


On Fri, Nov 27, 2015 at 11:54 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Henry Qin <root@hq6.me> writes:
>
>> Here is the question, copied below for your convenience:
>>
>> """
>> I am attempting to build git from source, and I would like make
>> install to put the binaries into a directory called dist in my source
>> directory, so I use the following configure line.
>>
>> ./configure --prefix=`pwd`/dist
>
> You probably want to use DESTDIR instead, e.g.
>
>     $ make prefix=/usr/local DESTDIR=/var/tmp/dest
>
> The standard way to phrase your question is "how do I 'make install'
> to install to a fake location so that I can tar up the result into a
> tarball?" (the key part being "so that..."), I think.
>

      reply	other threads:[~2015-11-28  7:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-28  7:19 Is it possible to build `git` such that the install directory and the deployment prefix is not the same? Henry Qin
2015-11-28  7:54 ` Junio C Hamano
2015-11-28  7:58   ` Henry Qin [this message]

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=CAO8bsPB98QRDRRftHNvLYafB-_EA_sbLMmB5SxxEjY+uRhKKCg@mail.gmail.com \
    --to=root@hq6.me \
    --cc=dennis@kaarsemaker.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).