ci: Fix the macOS and Windows builds - #93
Merged
Merged
Conversation
Both failures come from the runner images moving on, not from KDChart. macos-latest no longer ships the AGL framework, which Qt links QtGui against, so the shared build fails with "ld: framework 'AGL' not found" (QTBUG-137687). Qt removed that linkage in 6.9.2, so use 6.9.3. windows-latest is now Visual Studio 2025, whose STL dropped stdext, which Qt 5.15.2 still uses in qvarlengtharray.h. That combination cannot work and Qt 5.15.2 will not be fixed, so build Qt 5 on windows-2022 and keep Qt 6 on windows-latest. The job count is unchanged.
iamsergio
approved these changes
Aug 25, 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
2 participants
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.
CI has been red since early July. Both failures come from the runner images moving on, not from anything in KDChart.
macOS —
build (macos-latest, Debug, shared, 6.9.0):Qt links QtGui against the AGL framework, and the SDK on
macos-latestno longer ships it (QTBUG-137687). Qt removed that linkage in qtbase commitcdb33c3d562, which was backported and first released in 6.9.2 — two patch releases after the 6.9.0 we pin. Not backported to 6.8, so 6.9.2 or later is the minimum. This bumps the pin to 6.9.3.Windows —
build (windows-latest, Debug, shared, 5.15.2):windows-latestis now Visual Studio 2025, whose STL removed thestdextextension that Qt 5.15.2 uses. That combination cannot be made to work and Qt 5.15.2 will not gain a fix, so Qt 5 moves towindows-2022(the same image KDReports pins) while Qt 6 stays onwindows-latest, which is where new toolchain breakage actually shows up first.Coverage moves rather than shrinking, and the job count is unchanged — 8 matrix combinations, 2 excluded, 6 kept plus the existing
include, matching the 7 jobs of the last run:One note for review: the
excludeentries match bothqt_versionandarchitecturesrather thanqt_versionalone. GitHub documents partial matching for excludes, but every other KDAB repo using this pattern excludes aconfigthat has only one key, so nested partial matching is untested here — matching the full object is guaranteed to fire.