From: phillip.wood123@gmail.com
To: Eli Schwartz <eschwartz@gentoo.org>,
phillip.wood@dunelm.org.uk, Patrick Steinhardt <ps@pks.im>
Cc: Junio C Hamano <gitster@pobox.com>,
Henrik Holst <henrik.holst@outlook.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: ./configure fails to link test program due to missing dependencies
Date: Fri, 27 Sep 2024 11:00:39 +0100 [thread overview]
Message-ID: <b33076f2-ca01-4286-807c-f4b45a00d944@gmail.com> (raw)
In-Reply-To: <71ed5967-0302-42bc-97c7-81886408d688@gentoo.org>
Hi Eli
Thanks for this, it's useful to know how meson works with Visual Studio
On 26/09/2024 17:04, Eli Schwartz wrote:
> On 9/26/24 9:55 AM, Phillip Wood wrote:
>> 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.
>
>
> I can't really offer suggestions on what may or may not come
> preinstalled in Visual Studio. That thread does suggest the major
> problem cmake was trying to solve is:
>
> - having to install the git-for-windows sdk at all (is it still
> necessary? I guess so, because POSIX shell and perl and mingw
> runtimes. Unsure how either meson or cmake could solve this.)
If you've got git-for-windows installed then it has the POSIX and perl
bits that are required to run git and the CMake build uses those and
downloads any libraries it needs with vcpkg so you don't need the sdk.
> - people who are *unfamiliar with the command line and want a GUI*
>
>
> Meson has a trivially installable VS Code plugin that is supposed to
> handle setting up the project for you. You can generate either ninja
> projects or Visual Studio solutions. "One may need to install a plugin"
> is hopefully not as big a barrier to entry as "install a bunch of stuff
> then go to a shell and run make vcxproj". Is the criteria truly "must be
> one button click"?
Personally I think so long as there is a simple way to build git without
resorting to the command line that should be fine. It sounds like that's
the case with meson.
> [...]
> Stuff like "how painful is it for a Windows contributor to set up an SDK
> and then also go mess around with Makefile targets and then load the
> result into their IDE" is an interesting discussion to have but not
> quite the same as saying "go to the marketplace and install such and
> such plugin" is an obstacle.
Agreed
Best Wishes
Phillip
next prev parent reply other threads:[~2024-09-27 10:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-14 22:57 ./configure fails to link test program due to missing dependencies Henrik Holst
2024-09-15 16:37 ` Junio C Hamano
2024-09-15 16:47 ` brian m. carlson
2024-09-16 7:50 ` Patrick Steinhardt
2024-09-18 10:04 ` Phillip Wood
2024-09-18 22:39 ` Junio C Hamano
2024-09-24 12:10 ` Patrick Steinhardt
2024-09-24 13:59 ` Eli Schwartz
2024-09-24 14:25 ` Paul Smith
2024-09-25 4:36 ` Patrick Steinhardt
2024-09-25 6:02 ` Eli Schwartz
2024-09-25 6:04 ` Patrick Steinhardt
2024-09-26 13:55 ` Phillip Wood
2024-09-26 14:02 ` Patrick Steinhardt
2024-09-27 10:10 ` Phillip Wood
2024-09-26 16:04 ` Eli Schwartz
2024-09-27 10:00 ` phillip.wood123 [this message]
2024-09-26 16:22 ` Junio C Hamano
2024-09-29 17:56 ` Johannes Schindelin
2024-09-29 18:10 ` Eli Schwartz
2024-09-30 8:50 ` Phillip Wood
2024-09-30 13:57 ` Eli Schwartz
2024-09-30 16:31 ` Junio C Hamano
2024-09-30 16:05 ` Johannes Schindelin
2024-09-25 19:15 ` Patrick Steinhardt
2024-09-25 19:17 ` Patrick Steinhardt
2024-09-24 17:39 ` Junio C Hamano
2024-09-25 15:33 ` Paul Smith
2024-09-26 1:35 ` Eli Schwartz
2024-09-26 19:42 ` Paul Smith
2024-09-24 14:31 ` Eli Schwartz
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=b33076f2-ca01-4286-807c-f4b45a00d944@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=eschwartz@gentoo.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=henrik.holst@outlook.com \
--cc=jrnieder@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
/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).