Fix failing GitHub Actions "cmake" job on Windows#123
Open
DDvO wants to merge 14 commits into
Open
Conversation
DDvO
force-pushed
the
fix-Debian-packaging
branch
from
b99b703 to
d1a4344
Compare
Copilot
AI
changed the title
Fix Debian packaging
Fix failing GitHub Actions "cmake" job on Windows
Jun 15, 2026
… 2022" which meanwhile is no more available
…, following Copilot suggestion
DDvO
force-pushed
the
fix-Debian-packaging
branch
from
0b9ad18 to
d5b4fc0
Compare
…s adding version to lib name (libgencmp2)
DDvO
force-pushed
the
fix-Debian-packaging
branch
from
d5b4fc0 to
f99da80
Compare
DDvO
force-pushed
the
fix-Debian-packaging
branch
from
9fa01b3 to
811f101
Compare
…q}() consistent with OpenSSL
|
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.
The
cmakeCI job started failing on June 12, 2026 whenwindows-latestwas updated to thewindows-2025-vs2026runner image (Visual Studio 2026), which no longer includes Visual Studio 2022 (VS 17).Root Cause
The workflow hardcoded
-G "Visual Studio 17 2022"in both cmake invocations. When thewindows-latestrunner image changed to one that ships Visual Studio 2026 instead of VS 2022, cmake could no longer find any matching Visual Studio instance and failed at theproject()call.Fix
Removed the hardcoded
-G "Visual Studio 17 2022"generator flag from both cmake steps in.github/workflows/windows.yml, keeping only-A x64for the target architecture. CMake will now auto-detect the installed Visual Studio version, making the workflow resilient to future runner image updates.