-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Qt] Update to 6.8.0 #41534
[Qt] Update to 6.8.0 #41534
Conversation
Neumann-A
commented
Oct 12, 2024
•
edited
Loading
edited
- qtmultimedia:x64-linux fails due to gstreamer pc file containing a non-existant path.
- qtaplicationmanager:x64-linux: fails due to a missing systemd header? (Solved by not building the watchdog)
- qtaplicationmanager:arm64-windows: fails due to empty dirs
- Downstream errors in x64-windows-static-* needs to be investigated (due to open62541)
- open62541 needs a new release.
- tinyorm needs a newer release
/azp run |
Rerunning due to network mistake. |
Azure Pipelines successfully started running 1 pipeline(s). |
Closes #41441. |
…into update_qt_6.8.0
Is this on-hold for the planned 6.8.1 release on Nov 21? |
No just waiting for review. |
|
Actually @WangWeiLin-MV. |
Failing on "./vcpkg install qt" on MacOS
Also after build everything, it is impossible to add qmake to Qt Creator. It says - "Qt version is not properly installed, please run make install" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All versions/*
checked with vcpkg x-add-version
|
||
file(GLOB_RECURSE qttools "${CURRENT_PACKAGES_DIR}/tools/Qt6/bin/*") | ||
if(NOT qttools AND VCPKG_CROSSCOMPILING) | ||
file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/tools/Qt6/bin/") | ||
endif() | ||
|
||
if(VCPKG_TARGET_IS_WINDOWS AND VCPKG_CROSSCOMPILING AND VCPKG_TARGET_ARCHITECTURE STREQUAL "arm64") | ||
file(REMOVE_RECURSE | ||
"${CURRENT_PACKAGES_DIR}/bin/" | ||
"${CURRENT_PACKAGES_DIR}/debug/bin/" | ||
"${CURRENT_PACKAGES_DIR}/tools/" | ||
) | ||
endif() | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would this result in having to native-compiling for arm64 Windows?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should rather ask if VCPKG_TARGET_ARCHITECTURE STREQUAL "arm64"
can be removed and if the error also exists if you crosscompile from arm64 to x64 but i cannot answer that question since I cannot test it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is here check target architecture and delete these files? My local build takes a lot of time so can't test quickly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The local build of arm64-windows
on x64-windows
passed after removing this section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The local build of
arm64-windows
onx64-windows
passed after removing this section.
Did you have any failed local post-build checks? Removing these directories was made due to failed Azure pipeline: https://dev.azure.com/vcpkg/public/_build/results?buildId=108756&view=logs&jobId=84da4f4a-968a-5b5c-16e9-f444c845396d&j=84da4f4a-968a-5b5c-16e9-f444c845396d&t=410b6c71-3bf9-5b7a-84d3-17ae677a92aa
P.S. Native arm64-windows support can be improved in subsequent pull request (provided that anyone even cares about it). I think I'm not the only one looking forward to this getting merged for x64-windows, and *-linux.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you have any failed local post-build checks?
Yes, it passed locally.
Removing these directories was made due to failed Azure pipeline: https://dev.azure.com/vcpkg/public/_build/results?buildId=108756&view=logs&jobId=84da4f4a-968a-5b5c-16e9-f444c845396d&j=84da4f4a-968a-5b5c-16e9-f444c845396d&t=410b6c71-3bf9-5b7a-84d3-17ae677a92aa
Thanks for the information, I will look into this failure later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Recommended reporting to upstream https://bugreports.qt.io/browse/QTBUG-126817
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The source code has been modified, requires upstream confirmation or source link.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an include (order?) fix and doesn't require upstream confirmation according to the maintainer guidelines.
Don't ask me how upstream even compiled this since without this it runs static_assert assert that the forward declared classes are incomplete.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry, I missed this:
This is an include (order?) fix and doesn't require upstream confirmation according to the maintainer guidelines.
That's not correct. https://learn.microsoft.com/vcpkg/contributing/maintainer-guide#notify-upstream-owners-for-upstream-relevant-patches
We will skip this waiting period if we have high confidence that the change is correct. Examples of high confidence patches include, but are not limited to:
[...]
*Adding missing #includes.
We can merge stuff without upstream having accepted that does this, but there is still duty to notify.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The port qt
installation tests pass with the following triplets:
- arm64-windows
- x64-windows
Thanks for the update! |