Skip to content

Stabilize windows-latest build by removing conflicting Qt environment state - #176

Draft
mermerico with Copilot wants to merge 2 commits into
devfrom
copilot/fix-windows-latest-build
Draft

Stabilize windows-latest build by removing conflicting Qt environment state#176
mermerico with Copilot wants to merge 2 commits into
devfrom
copilot/fix-windows-latest-build

Conversation

Copilot AI commented Jul 5, 2026

Copy link
Copy Markdown

The windows-latest-build job 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)

    • Added a Windows-only step in .github/workflows/cmake.yml before Configure CMake.
    • Clears Qt5_DIR, Qt6_DIR, QTDIR, and CMAKE_PREFIX_PATH if present, preventing host-runner Qt contamination.
  • Impact

    • Keeps dependency resolution aligned with the selected vcpkg triplet/toolchain in CI.
    • Avoids mixed Qt headers/libs that produced unresolved Qt symbols in windows-latest-build.
- name: Clear conflicting Qt environment (Windows)
  if: runner.os == 'Windows'
  shell: pwsh
  run: |
    @('Qt5_DIR', 'Qt6_DIR', 'QTDIR', 'CMAKE_PREFIX_PATH') | ForEach-Object {
        if (Test-Path "env:$_") {
            Remove-Item "env:$_"
        }
    }

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
Copilot AI requested a review from mermerico July 5, 2026 04:39
@mermerico
mermerico changed the base branch from master to dev July 5, 2026 04:55
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