From: Phillip Wood <phillip.wood123@gmail.com>
Date: Wed, 18 Sep 2024 10:04:54 GMT
Subject: Re: ./configure fails to link test program due to missing dependencies
Message-ID: <29c5c9c0-aa61-415a-9cfa-d64a6b946a48@gmail.com>
In-Reply-To: <ZufjWR6AJM-DIWPR@pks.im>

Hi Patrick

On 16/09/2024 08:50, Patrick Steinhardt wrote:
> 
> I sometimes wonder whether we should move on and discard one of the
> three build systems we have: plain GNU Make, autoconf and CMake. And
> from these three I'd rather want to throw the autoconf-based thing away:
> 
>    - The Makefile is probably what most people use, so throwing it out is
>      a no-go right now.
> 
>    - CMake is really useful because it has support for IDEs and
>      alternatives to GNU Make like Ninja, which builds Git way faster
>      than Makefiles. It also has support for out-of-tree builds, which I
>      find rather useful.
> 
> So is there a path forward to move CMake support out of contrib/, make
> it an officially supported way to build Git and then throw away the
> autoconf-based infra? I'm not the biggest fan of CMake myself and very
> much prefer Meson, but we already have it wired up and thus I'm trying
> to be at least a bit pragmatic.

We seem to get fairly regular bug reports about the configure script, 
presumably because most contributors are using the Makefile. It would 
certainly be nice if we could get the CMake support into a state where 
we could consider dropping the configure script.

Best Wishes

Phillip