From b9ab5f3c0dc72ad1a9d01ab1d262965df99431a2 Mon Sep 17 00:00:00 2001 From: Eric Brumer Date: Fri, 17 Jul 2026 14:54:12 -0700 Subject: [PATCH] Clarify version prefix for Visual Studio Command Prompt Updated instructions for starting Visual Studio Command Prompt to reflect changes in version specification. --- docs/overview/acquire-msvc.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/overview/acquire-msvc.md b/docs/overview/acquire-msvc.md index cbd86ef454..b70d02b277 100644 --- a/docs/overview/acquire-msvc.md +++ b/docs/overview/acquire-msvc.md @@ -184,10 +184,10 @@ cmake -G "Visual Studio 18 2026" -T "version=14.52" ..\ Some build systems need the command prompt to have the `PATH`, `LIB`, `INCLUDE`, and related environment variables set before you run them. -To start a Visual Studio Command Prompt that targets a supported Build Tools version, add `-vcvars_ver=` where `` matches the folder name under `\VC\Tools\MSVC\`. +To start a Visual Studio Command Prompt that targets a supported Build Tools version, add `-vcvars_ver=` where `` matches the prefix of a folder name under `\VC\Tools\MSVC\`. ```cmd -\VC\Auxiliary\Build\vcvars64.bat -vcvars_ver=14.50.35717 +\VC\Auxiliary\Build\vcvars64.bat -vcvars_ver=14.50 ``` To start a Visual Studio Command Prompt targeting the MSVC preview tools, use `-vcvars_ver=preview`: