-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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 #26974
Comments
It's also ignoring my flag |
I can't reproduce this behavior on my machine. The option
|
I'm having this issue as well on my ThinkPad x13s when trying to install qt5-base with vcpkg version
|
I found a mitigation of sorts which got me farther which was to just edit the hostArch = $$QMAKE_HOST.arch
equals(hostArch, x86_64): \
hostArch = amd64
!equals(arch, $$hostArch): \
- arch = $${hostArch}_$$arch
+ arch = amd64_$$arch
isEmpty(MSVC_VER): \ Now I am getting |
@Wunkolo, I'm facing the same issue. Impossible to build |
@N0un I don't have any updates unfortunately. I'm stuck at the |
Probably this required: https://gist.github.com/thomaslmiller/b97bc7c7905f6e5fdfb93ee71e2a2fc5 |
I try it , it does not work. |
I just change this one, it maybe work, it is starting building now. what is 'jom' error? |
This change works for me, and QT5 could compile and build successful on windows on arm. |
o, it also work on my pc, let me ask the msft. |
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. |
Package: qt5-base[core]:arm64-windows -> 5.15.6#1
Host Environment
vcpkg-scripts version: 57d3194 2022-09-23 (34 hours ago)
To Reproduce
vcpkg install qt5-base
Failure logs
V:\buildtrees\qt5-base\config-arm64-windows-dbg-out.log
V:\buildtrees\qt5-base\config-arm64-windows-dbg-err.log
Appears to be a silly breakdown in
mkspecs/features/toolchain.prf
around line 319 where the "Unknown_arm64" line ends up being produced. It seems the correct line should be "amd64_arm64". Building natively on Windows 11 on a Galaxy Book Go -- aiming for an all-native ARM64 system!The text was updated successfully, but these errors were encountered: