Skip to content

Use 'vswhere' for VS compiler detection#115

Open
ralphlange wants to merge 4 commits into
epics-base:masterfrom
ralphlange:use-vswhere
Open

Use 'vswhere' for VS compiler detection#115
ralphlange wants to merge 4 commits into
epics-base:masterfrom
ralphlange:use-vswhere

Conversation

@ralphlange

Copy link
Copy Markdown
Contributor

Use vswhere for compiler detection of 'vs' setting

  • Use the 'vswhere' tool to automatically resolve the Visual Studio compiler location
    when the generic 'vs' compiler setting is specified.
  • Fall back to the hardcoded list of locations only if vswhere is not available on the system.
  • If a single installation is found, auto-select it; if multiple versions are found,
    print the options and raise a ValueError.

Co-authored-by: google-labs-jules[bot]
closes #112; closes #113

ralphlange and others added 4 commits July 14, 2026 19:14
As of May 2026, GHA uses new windows-2025 runners
that have vs2026 installed (instead of vs2022)
(closes epics-base#112)
- Use the 'vswhere' tool to automatically resolve
  the Visual Studio compiler location
  when the generic 'vs' compiler setting is specified.
- Fall back to the hardcoded list of locations
  only if vswhere is not available on the system.
- If a single installation is found, auto-select it;
  if multiple versions are found,
  print the options and raise a ValueError.

Co-authored-by: google-labs-jules[bot]
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.

cue.py fails with KeyError 'vs2022' on GitHub Actions windows-2025-vs2026

1 participant