-
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
[qt5-base] Build error #35031
Comments
Issue happens on an ARM64 machine - so no cross compiling involved. |
The culprit is in mkspecs/features/toolchain.prf
In case of host architecture is ARM64 $$QMAKE_HOST.arch is "unknown" - so an invalid arch is set when calling vcvarsall.bat. Assuming $$QMAKE_HOST.arch cannot be fixed trivially, it should be at least checked if $$QMAKE_HOST.arch is "unknown". In this case set hostArch="arm64" Something like below:
Above change enables not only arm64 native builds but also cross compilation arm64->amd64 |
@Gerdya Could you please submit a PR? :) |
@FrankXie05 I will submit a PR if I find the file in question. Can you please tell me the right upstream repository? |
@Gerdya You can submit a PR for vcpkg. And this is QT bug report: https://bugreports.qt.io/projects/QTBUG/issues |
This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment. |
This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment. |
Fixed by #41536 |
Package: qt5-base:arm64-windows -> 5.15.11#1
Host Environment
vcpkg-scripts version: 11610ea 2023-11-10 (43 minutes ago)
To Reproduce
vcpkg install qt5
Failure logs
C:\Users\mirko\source\repos\vcpkg\buildtrees\qt5-base\config-arm64-windows-dbg-out.log
C:\Users\mirko\source\repos\vcpkg\buildtrees\qt5-base\config-arm64-windows-dbg-err.log
The text was updated successfully, but these errors were encountered: