From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Paul Smith <paul@mad-scientist.net>
Cc: Git mailing list <git@vger.kernel.org>, Dan Jacques <dnj@google.com>
Subject: Re: Git 2.18: RUNTIME_PREFIX... is it working?
Date: Fri, 6 Jul 2018 11:00:00 +0200 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1807061059260.75@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <986185d30a0f09b4e2a9832d324a265cd3da7354.camel@mad-scientist.net>
Hi Paul,
On Thu, 5 Jul 2018, Paul Smith wrote:
> On Wed, 2018-07-04 at 13:22 +0200, Johannes Schindelin wrote:
> > > Basically what happens is that I run configure with
> > > --prefix=/my/install/path --with-gitconfig=etc/gitconfig
> > > --with-gitattributes=etc/gitattributes.
> > >
> > > Then I run make with RUNTIME_PREFIX=YesPlease.
> >
> > Ah. In Git for Windows, we do not use configure. I *think* this
> > points to an incompatibility of the RUNTIME_PREFIX feature with our
> > autoconf support, and this is a grand opportunity for you to step in
> > and help.
> >
> > Essentially, what you will want to do is to implement a new configure
> > option --with-runtime-prefix that then prevents the autoconf script
> > from munging the relative paths in the way it does.
>
> FYI I was able to get this to work by overriding variables on the make
> command line, like this:
>
> make ... RUNTIME_PREFIX=YesPlease \
> gitexecdir=libexec/git-core \
> template_dir=share/git-core/templates \
> sysconfdir=etc
>
> I agree a new autoconf option would be much simpler to use. I'll think
> about it as I happen to have some some experience in these areas ;) ...
I look forward to reviewing this...
> but time is limited of course :).
Yep. Same here ;-)
Ciao,
Johannes
next prev parent reply other threads:[~2018-07-06 9:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 5:12 Git 2.18: RUNTIME_PREFIX... is it working? Paul Smith
2018-07-04 11:22 ` Johannes Schindelin
2018-07-05 15:36 ` Paul Smith
2018-07-06 9:00 ` Johannes Schindelin [this message]
2018-07-06 13:18 ` Daniel Jacques
2018-07-08 18:52 ` Paul Smith
2018-07-08 21:52 ` Johannes Schindelin
2018-07-09 19:58 ` Jeff King
2018-07-09 20:26 ` Johannes Schindelin
2018-07-10 2:21 ` Jeff King
2018-07-10 11:40 ` Johannes Schindelin
2018-07-10 14:03 ` Daniel Jacques
2018-07-10 16:09 ` Junio C Hamano
2018-07-09 21:05 ` Junio C Hamano
2018-07-10 3:56 ` Jeff King
2018-07-10 7:13 ` Perry Hutchison
2018-07-10 14:03 ` Jeff King
2018-07-10 22:20 ` Jonathan Nieder
2018-07-10 22:21 ` Jonathan Nieder
2018-07-17 9:45 ` Johannes Schindelin
2018-07-14 20:51 ` brian m. carlson
2018-07-18 12:18 ` Johannes Schindelin
2018-07-19 22:26 ` brian m. carlson
2018-07-20 14:29 ` Jeff Hostetler
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1807061059260.75@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=dnj@google.com \
--cc=git@vger.kernel.org \
--cc=paul@mad-scientist.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).