From 73ef8efee4cfbfbda31387a413bd9bf73f9da44d Mon Sep 17 00:00:00 2001 From: Lars Froehlich Date: Mon, 31 Aug 2026 14:57:48 +0200 Subject: [PATCH] Add support for Visual Studio 2026 [why] The heuristics for finding the VS toolchain did not know about VS 2026 yet. [how] Add "18" to the list of possible subfolder names under C:\Program Files\Microsoft Visual Studio. Yes, apparently VS 2026 uses "18" where its predecessors used "2022", "2019", or "2017". --- tools/make_vs.bat | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/tools/make_vs.bat b/tools/make_vs.bat index dce21d39..58feb640 100644 --- a/tools/make_vs.bat +++ b/tools/make_vs.bat @@ -115,14 +115,20 @@ ninja -C "%REPO_ROOT%%FOLDER%" %TARGET% exit /B 1 ) - @IF EXIST "%VC_PREFIX%2022" ( + @IF EXIST "%VC_PREFIX%18" ( + @REM Visual Studio 2026 uses "18" instead of "2026" as a folder name + set VC_YEAR=18\ + ) ELSE IF EXIST "%VC_PREFIX%2022" ( set VC_YEAR=2022\ ) ELSE IF EXIST "%VC_PREFIX%2019" ( set VC_YEAR=2019\ ) ELSE IF EXIST "%VC_PREFIX%2017" ( set VC_YEAR=2017\ ) ELSE ( - echo "Can not find '%VC_PREFIX%2022', '2019', or '2017'" + echo "Can not find '%VC_PREFIX%18', '%VC_PREFIX%2022', '%VC_PREFIX%2019', or '%VC_PREFIX%2017'" + C: + chdir "%VC_PREFIX%" + dir exit /B 1 )