Skip to content

Let ClangCL preset auto-detect the Visual Studio generator#98

Merged
thetic merged 1 commit into
mainfrom
fix-clangcl-vs-generator
Jul 10, 2026
Merged

Let ClangCL preset auto-detect the Visual Studio generator#98
thetic merged 1 commit into
mainfrom
fix-clangcl-vs-generator

Conversation

@thetic

@thetic thetic commented Jul 10, 2026

Copy link
Copy Markdown
Owner

Summary

  • windows-latest now points to windows-2025, which ships Visual Studio 18 (2025)
  • The ClangCL preset had "generator": "Visual Studio 17 2022" hardcoded, causing CMake to fail with could not find any instance of Visual Studio
  • The MSVC preset never specified a generator and works fine because CMake auto-detects whatever VS version is installed
  • Remove the explicit generator from ClangCL so it does the same

@coveralls

coveralls commented Jul 10, 2026

Copy link
Copy Markdown

Coverage Status

No base build to compare — fix-clangcl-vs-generator into main

The hardcoded "Visual Studio 17 2022" generator broke when windows-latest
moved to windows-2025, which ships VS 18. Dropping the explicit generator
lets CMake pick whatever VS version is installed, matching the behaviour of
the MSVC preset.
@thetic
thetic force-pushed the fix-clangcl-vs-generator branch from b677d0c to 8046049 Compare July 10, 2026 03:52
@thetic
thetic merged commit a81cdba into main Jul 10, 2026
40 checks passed
@thetic
thetic deleted the fix-clangcl-vs-generator branch July 10, 2026 03:53
@github-actions

github-actions Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor
TestsPassed ✅Skipped ⚠️Failed
JUnit Tests1064 ran1055 passed9 skipped0 failed

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