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

Re: ./configure fails to link test program due to missing dependencies

From
Patrick Steinhardt <ps@pks.im>
Date
Sep 26, 2024, 14:02 UTC
Message-ID
<ZvVpcY5Jgp7BzuRu@pks.im>
In-Reply-To
<3a303c6e-35b0-4428-9d23-799b33194330@gmail.com>
On Thu, Sep 26, 2024 at 02:55:52PM +0100, Phillip Wood wrote:
Show 24 quoted lines
> Hi Patrick
> 
> On 25/09/2024 07:04, Patrick Steinhardt wrote:
> > On Wed, Sep 25, 2024 at 02:02:34AM -0400, Eli Schwartz wrote:
> > 
> > > I'm probably biased, but some of these failure modes are *weird*. And
> > > they basically never require the CMakeLists.txt to do something
> > > considered non-idiomatic in order to trigger the issue.
> > 
> > All of this is very valuable data to make my case for Meson instead of
> > CMake. Appreciated, thanks!
> 
> One thing to bear in mind is why our CMakeLists.txt was introduced in the
> first place [1]. Visual Studio's CMake integration means that so long as
> git-for-windows is installed building git is simply a case of clicking on a
> button, there is no need to install extra software or plugins. I'm not sure
> the same is true for meson and I don't think we want to end up supporting
> both.
> 
> Best Wishes
> 
> Phillip
> 
> [1] https://lore.kernel.org/git/nycvar.QRO.7.76.6.2004251354390.18039@tvgsbejvaqbjf.bet/

Fair enough. The final discussion about which build system to pick is of course still to be had. Having worked with both CMake and Meson quite a bit in the past I'm strongly in favor of Meson myself, and so I will try to make a strong case for it. But points like this of course need to be considered when we have the discussion.

The nice thing is that we'll then have all serious contenders (that I am aware of) wired up, even though the level of support will be different across them. But it should allow folks to come to a better understanding of what they will be signing up for.

In any case, I'm now in a state where the Meson-based build works and tests just fine, except for t0200, which requires a bit more plumbing to set up xgettext infra. Once I'm done with that I'll go off and test with both macOS and Windows to check how the experience is over there. I hope to be done with that somewhen next week, at which point I'll send things to the mailing list.

Patrick
Previous: Phillip WoodNext: Phillip Wood
Message 14 of 31 in “./configure fails to link test program due to missing dependencies”
  1. Henrik HolstSep 14, 2024
  2. Junio C HamanoSep 15, 2024
  3. brian m. carlsonSep 15, 2024
  4. Patrick SteinhardtSep 16, 2024
  5. Phillip WoodSep 18, 2024
  6. Junio C HamanoSep 18, 2024
  7. Patrick SteinhardtSep 24, 2024
  8. Eli SchwartzSep 24, 2024
  9. Paul SmithSep 24, 2024
  10. Patrick SteinhardtSep 25, 2024
  11. Eli SchwartzSep 25, 2024
  12. Patrick SteinhardtSep 25, 2024
  13. Phillip WoodSep 26, 2024
  14. Patrick SteinhardtSep 26, 2024
  15. Phillip WoodSep 27, 2024
  16. Eli SchwartzSep 26, 2024
  17. phillip.wood123@gmail.comSep 27, 2024
  18. Junio C HamanoSep 26, 2024
  19. Johannes SchindelinSep 29, 2024
  20. Eli SchwartzSep 29, 2024
  21. Phillip WoodSep 30, 2024
  22. Eli SchwartzSep 30, 2024
  23. Junio C HamanoSep 30, 2024
  24. Johannes SchindelinSep 30, 2024
  25. Patrick SteinhardtSep 25, 2024
  26. Patrick SteinhardtSep 25, 2024
  27. Junio C HamanoSep 24, 2024
  28. Paul SmithSep 25, 2024
  29. Eli SchwartzSep 26, 2024
  30. Paul SmithSep 26, 2024
  31. Eli SchwartzSep 24, 2024

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.