Normalize Visual Studio kit target arch for ${buildKitTargetArch}#4680
Draft
Normalize Visual Studio kit target arch for ${buildKitTargetArch}#4680
Conversation
Copilot
AI
changed the title
[WIP] Fix unknown ${buildKitTargetArch} in Visual Studio Kits
Fix ${buildKitTargetArch} resolution for Visual Studio kits
Jan 30, 2026
Co-authored-by: hanniavalera <90047725+hanniavalera@users.noreply.github.com>
c4a35ad to
79d921e
Compare
Co-authored-by: hanniavalera <90047725+hanniavalera@users.noreply.github.com>
Copilot
AI
changed the title
Fix ${buildKitTargetArch} resolution for Visual Studio kits
Normalize Visual Studio kit target arch for ${buildKitTargetArch}
Feb 12, 2026
Contributor
|
@copilot arm64 is just a alias of aarch64 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This changes visible behavior
The following changes are proposed:
${buildKitTargetArch}expands correctly.arm64and related VS kit cases.constfor targetArch) to keep the mapping clean.The purpose of this change
Ensure build directory and other substitutions use the selected VS kit architecture (e.g.,
build/x64instead ofbuild/unknown).Other Notes/Information
Example:
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
update.code.visualstudio.com/opt/hostedtoolcache/node/24.13.0/x64/bin/node /opt/hostedtoolcache/node/24.13.0/x64/bin/node ./out/test/unit-tests/runTest.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
This section details on the original issue you should resolve
<issue_title>[Bug] ${buildKitTargetArch} is 'unknown' for Visual Studio Kits</issue_title>
<issue_description>### Brief Issue Summary
When using ${buildKitTargetArch} as Variable substitution in Build Directory (${workspaceFolder}/build/${buildKitTargetArch}) for Visual Studio Kits (tested in Visual Studio Professional 2019 and 2022 Release) the created folder is 'build/unknown' for all target architectures:
CMake Tools Diagnostics
{ "os": "win32", "vscodeVersion": "1.103.1", "cmtVersion": "1.22.7", "configurations": [ { "folder": "e:\\DeltaIdPlus\\OCR\\cpp", "cmakeVersion": "4.1.1", "configured": false, "generator": "Visual Studio 17 2022", "usesPresets": false, "compilers": {} } ], "cpptoolsIntegration": { "isReady": false, "hasCodeModel": false, "activeBuildType": "", "buildTypesSeen": [], "requests": [], "responses": [], "partialMatches": [], "targetCount": 0, "executablesCount": 0, "librariesCount": 0, "targets": [] }, "settings": [ { "communicationMode": "automatic", "useCMakePresets": "auto", "configureOnOpen": true } ] }Debug Log
Additional Information
No response</issue_description>
<agent_instructions>You are Copilot coding agent acting as a senior maintainer/contributor for the VS Code extension repository microsoft/vscode-cmake-tools.
You are deeply familiar with CMake, CMake Presets, CTest, ki...
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.