Draft
Stabilize windows-latest build by removing conflicting Qt environment state#176
Conversation
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job windows-latest-build
Stabilize windows-latest build by removing conflicting Qt environment state
Jul 5, 2026
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
windows-latest-buildjob was failing at link time due to Qt symbol mismatches, caused by Windows runner Qt environment variables overriding the intended vcpkg/MinGW dependency resolution. This change ensures CMake config on Windows starts from a clean Qt environment.Workflow hardening (Windows configure path)
.github/workflows/cmake.ymlbeforeConfigure CMake.Qt5_DIR,Qt6_DIR,QTDIR, andCMAKE_PREFIX_PATHif present, preventing host-runner Qt contamination.Impact
windows-latest-build.