All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH 2/3] contrib/buildsystems: drop support for building .vcproj/.vcxproj files
Date: Mon, 5 May 2025 15:24:57 +0200	[thread overview]
Message-ID: <aBi8KQWP4YAi6Gph@pks.im> (raw)
In-Reply-To: <1ec2a4bb1d58ea8cfa6abb2a0e625ef3e0db2a1f.1746430790.git.gitgitgadget@gmail.com>

On Mon, May 05, 2025 at 07:39:49AM +0000, Johannes Schindelin via GitGitGadget wrote:
> From: Johannes Schindelin <johannes.schindelin@gmx.de>
> 
> Before we had CMake support, the only way to build Git in Visual Studio
> was via this hacky `generate` script.
> 
> For a while I tried to fix whenever things got broken, in particular to
> allow building confidence in embargoed releases by running the CI builds
> in Azure Pipelines in a private Azure DevOps project. I even carried the
> patches in Git for Windows with the intention of upstreaming them,
> eventually.
> 
> However, it is a lot of work with too little benefit. CMake is much
> better supported by Visual Studio. So let's drop this hacky script (plus
> support code).

Makes sense. This made me wonder whether we also want to get rid of
"contrib/vscode", which is similar in spirit. Both Meson and CMake can
be used natively with VSCode.

Thanks for working on these cleanups!

Patrick

  reply	other threads:[~2025-05-05 13:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05  7:39 [PATCH 0/3] Some CI/buildsystems cleanup Johannes Schindelin via GitGitGadget
2025-05-05  7:39 ` [PATCH 1/3] ci: stop linking the `prove` cache Johannes Schindelin via GitGitGadget
2025-05-05  7:39 ` [PATCH 2/3] contrib/buildsystems: drop support for building .vcproj/.vcxproj files Johannes Schindelin via GitGitGadget
2025-05-05 13:24   ` Patrick Steinhardt [this message]
2025-05-05 13:46     ` Johannes Schindelin
2025-05-05 14:33       ` Patrick Steinhardt
2025-06-02  8:38   ` Johannes Schindelin
2025-06-02 15:04     ` Junio C Hamano
2025-05-05  7:39 ` [PATCH 3/3] config.mak.uname: drop the `vcxproj` target Johannes Schindelin via GitGitGadget
2025-05-05 13:52 ` [PATCH 0/3] Some CI/buildsystems cleanup Junio C Hamano

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=aBi8KQWP4YAi6Gph@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.