Skip to content

fix(windows): require VC tools in vswhere discovery#138

Merged
proggeramlug merged 1 commit intoPerryTS:mainfrom
NicoAvanzDev:fix/windows-vswhere-vc-tools
Apr 22, 2026
Merged

fix(windows): require VC tools in vswhere discovery#138
proggeramlug merged 1 commit intoPerryTS:mainfrom
NicoAvanzDev:fix/windows-vswhere-vc-tools

Conversation

@NicoAvanzDev
Copy link
Copy Markdown
Contributor

@NicoAvanzDev NicoAvanzDev commented Apr 22, 2026

Summary

  • Require Microsoft.VisualStudio.Component.VC.Tools.x86.x64 in Windows vswhere queries so -latest no longer resolves SQL Server Management Studio instead of a real MSVC install.
  • Apply the filtered query to MSVC linker discovery, MSVC LIB path lookup, doctor, and bundled Visual Studio clang detection.
  • Add a Windows regression test that locks the vswhere args to the VC-tools-filtered query.

Testing

  • cargo build -p perry
  • cargo test -p perry-codegen --lib
  • cargo test -p perry

Require `Microsoft.VisualStudio.Component.VC.Tools.x86.x64` in Windows
`vswhere` queries so `-latest` no longer resolves SQL Server Management
Studio (or any other VS-shell install without MSVC tooling) instead of a
real C++ build-tools install.

Applies the filtered query to MSVC linker discovery
(`find_msvc_link_exe`), MSVC `LIB` path lookup (`find_msvc_lib_paths`),
`doctor`'s linker check, and bundled Visual Studio `clang.exe` detection
(`find_msvc_bundled_clang`).

Adds a Windows-gated regression test pinning the exact `vswhere` arg
list so the `-requires` flag can't be silently dropped in a future
refactor.
@proggeramlug proggeramlug force-pushed the fix/windows-vswhere-vc-tools branch from 1cda92b to 76f30c8 Compare April 22, 2026 13:10
@proggeramlug proggeramlug merged commit 9033dd4 into PerryTS:main Apr 22, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants