Skip to content

[Qt] Update to 6.9.2#47416

Closed
kimbirkelund wants to merge 16 commits intomicrosoft:masterfrom
kimbirkelund:kbi/qt-6_9_2
Closed

[Qt] Update to 6.9.2#47416
kimbirkelund wants to merge 16 commits intomicrosoft:masterfrom
kimbirkelund:kbi/qt-6_9_2

Conversation

@kimbirkelund
Copy link

@kimbirkelund kimbirkelund commented Sep 19, 2025

  • Changes comply with the maintainer guide.
  • SHA512s are updated for each updated download.
  • The "supports" clause reflects platforms that may be fixed by this new version.
  • Any fixed CI baseline entries are removed from that file.
  • Any patches that are no longer applied are deleted from the port's directory.
  • The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
  • Only one version is added to each modified port's versions file.

This is my first PR updating a port. I've modeled it on this PR updating Qt to 6.9.1.

@JavierMatosD JavierMatosD marked this pull request as draft September 19, 2025 16:24
@petersteneteg
Copy link
Contributor

Looking forward to this update, since qtbase 6.9.1 fails to build with Xcode 26!

@kimbirkelund
Copy link
Author

Yeah, that was my motivation 🙂

@kimbirkelund
Copy link
Author

The x86-windows, arm64-osx and x64-osx build is failing on qtbase[sql-oci] with the following error:

CMake Error at cmake/QtBuildInformation.cmake:554 (message):
  Feature "sql_oci": Forcing to "ON" breaks its condition:

      Oracle_FOUND

  Condition values dump:

      Oracle_FOUND = "FALSE"

Call Stack (most recent call first):
  cmake/QtFeature.cmake:786 (qt_configure_add_report_error)
  cmake/QtFeature.cmake:923 (qt_feature_check_and_save_internal_value)
  cmake/QtFeature.cmake:1192 (qt_evaluate_feature)
  src/plugins/sqldrivers/CMakeLists.txt:46 (qt_feature_module_end)

I don't know what to do about that.

@kimbirkelund
Copy link
Author

The arm64-osx and x64-osx builds are failing on qtwayland[core] with the following error:

CMake Warning at ports/qtwayland/portfile.cmake:4 (message):
  qtwayland requires libwayland-dev from your system package manager.  You
  can install it with

  sudo apt install libwayland-dev

  on Ubuntu systems.
Call Stack (most recent call first):
  scripts/ports.cmake:206 (include)

I don't know what to do about that.

@dg0yt
Copy link
Contributor

dg0yt commented Sep 22, 2025

qtbase[sql-oci] is an expected failure in CI. It needs an SDK from Oracle. No action needed.

@dg0yt
Copy link
Contributor

dg0yt commented Sep 22, 2025

qtwayland(android | osx) is an expected failure in CI. No action needed.

(You find these entries in scripts/ci.features.baseline.txt.)

@dg0yt
Copy link
Contributor

dg0yt commented Sep 22, 2025

The unexpected error is qtinterfaceframework.

-- Fetching https://code.qt.io/qt/qtinterfaceframework.git d7f7b3e722070d056dff0ea098bda3d098dc991a...
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
    Command failed: /usr/bin/git fetch https://code.qt.io/qt/qtinterfaceframework.git d7f7b3e722070d056dff0ea098bda3d098dc991a --depth 1 -n
    Working Directory: /vcpkg/downloads/git-tmp
    Error code: 128
    See logs for more information:
      /mnt/vcpkg-ci/b/qtinterfaceframework/git-fetch-x64-linux-err.log

Raw git? Flaky by design. No asset caching.

@kimbirkelund
Copy link
Author

Thanks for the input. Is there an easy way to see which should just be ignored? Since both the "real" and ignored errors show up in the log artifacts?

Also qt3d[vulkan] fails on mac, because it depends on qtbase[vulkan] which is expected to fail. Does that mean that qt3d[vulkan] is implicitly ignored, or should that be added to the baseline file?

@kimbirkelund
Copy link
Author

The unexpected error is qtinterfaceframework.
...
Raw git? Flaky by design. No asset caching.

I've wondered a bit about that one. It wasn't updated automatically in the qt_port_data.cmake hash list - and I can't actually remember where I got the hash I entered from.

@dg0yt
Copy link
Contributor

dg0yt commented Sep 22, 2025

Is there an easy way to see which should just be ignored? Since both the "real" and ignored errors show up in the log artifacts?

In the AZP output for x64-windows-static-md, I cannot see explict hints for expected failures, but there is

There are some feature test problems!
D:\a\_work\1\s\scripts\azure-pipelines/../ci.feature.baseline.txt: error: qtinterfaceframework[core]:x64-windows-static build failed but was expected to pass
note: consider adding `qtinterfaceframework=fail`, or `qtinterfaceframework:x64-windows-static=fail`, or equivalent skips
note: if some features are required, consider effectively always enabling those parts in portfile.cmake for qtinterfaceframework, or consider adding `qtinterfaceframework[required-feature]=options` to include 'required-feature' in all tests

The expectedd failures are in scripts/ci.*.

@adriweb
Copy link

adriweb commented Oct 4, 2025

Note that 6.9.3 fixes building on macOS 26 due to a framework being linked that became unavailable.
Might be worth looking into updating to this version directly (or backporting the patch if it's easier for now)

@kimbirkelund
Copy link
Author

kimbirkelund commented Oct 4, 2025 via email

@xavier2k6
Copy link
Contributor

Qt 6.10.0 is officially out now!

@kimbirkelund
Copy link
Author

Great - doubt that's within my abilities... :-)

@xavier2k6 xavier2k6 mentioned this pull request Oct 10, 2025
@kimbirkelund
Copy link
Author

Superceded by #47735.

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.

5 participants