From 790c43debe884ddd9fea4f73e6da4b0cc07fe934 Mon Sep 17 00:00:00 2001 From: Eli Schwartz Date: Sun, 29 Sep 2024 14:20:36 -0400 Subject: [PATCH] docs: update the Visual Studio guide for the post-0.59 era with automatic vsenv For many years now, meson hasn't required manually entering a Visual Studio command prompt but has autodetected it. This confuses some readers of this outdated documentation into thinking it is much harder than it is. --- docs/markdown/Using-with-Visual-Studio.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/docs/markdown/Using-with-Visual-Studio.md b/docs/markdown/Using-with-Visual-Studio.md index 2680e8baf..c6a0806a5 100644 --- a/docs/markdown/Using-with-Visual-Studio.md +++ b/docs/markdown/Using-with-Visual-Studio.md @@ -5,9 +5,17 @@ short-description: How to use Meson in Visual Studio # Using with Visual Studio In order to generate Visual Studio projects, Meson needs to know the -settings of your installed version of Visual Studio. The only way to -get this information is to run Meson under the Visual Studio Command -Prompt. +settings of your installed version of Visual Studio. + + +The traditional way to get this information is to run Meson (or any build +system) under the Visual Studio Command Prompt. + +If no Visual Studio Command Prompt was detected, and no mingw compilers are +detected either, meson will attempt to find "a" Visual Studio installation for +you automatically, by asking Microsoft's "vswhere" program. If you want to +ignore mingw compilers, pass the `--vsenv` option on the meson command line. +If you need to guarantee a specific Visual Studio version, set it up manually. You can always find the Visual Studio Command Prompt by searching from the Start Menu. However, the name is different for each Visual Studio