git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Install-prefix when building should not be hardcoded

From
Ddarkdragon <darkdragon-001@web.de>
Date
Oct 5, 2022, 20:23 UTC
Message-ID
<CAAOCJVAAwgECsJPfm7eHOMmKPewJzxHTKhjwacxPRYWJkSpX_g@mail.gmail.com>
In-Reply-To
<xmqqczb6oyie.fsf@gitster.g>
On Wed, Oct 5, 2022 at 9:34 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 14 quoted lines
>
> Đoàn Trần Công Danh  <congdanhqx@gmail.com> writes:
>
> > On 2022-10-04 09:38:24+0200, darkdragon <darkdragon-001@web.de> wrote:
> >> Even though in Makefile, it is stated that git will figure out
> >> gitexecdir at runtime based on the path to the executable, there are
> >> many output files where $(prefix) will be hardcoded. Even git
> >> --exec-path will print out $(compile_prefix)/libexec/git-core instead
> >> of using run_prefix.
> >
> > I'm not sure about this part.
>
> Perhaps it is related to the use of RUNTIME_PREFIX (which I don't
> use myself)?
This seems to do the trick! Thanks a lot!
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 7 in “Install-prefix when building should not be hardcoded”
  1. darkdragonOct 4, 2022
  2. Đoàn Trần Công DanhOct 4, 2022
  3. darkdragonOct 4, 2022
  4. Junio C HamanoOct 5, 2022
  5. darkdragonOct 5, 2022
  6. Junio C HamanoOct 5, 2022
  7. Makefile: clarify runtime relative gitexecdirĐoàn Trần Công Danh, Oct 6, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.