Error building QT5 on Windows #6833
Assignees
Labels
requires:repro
The issue is not currently repro-able
Comments
|
what do these log files say? See logs for more information: |
|
@TheScarfix Thank you for your reply. The content in D:\GitHub\vcpkg\buildtrees\qt5-base\build-x86-windows-rel-err.log |
|
looks like a problem with ANGLE, not qt 🤔 |
|
@TheScarfix Do you have any suggestion about this bug reporting or something I could do? Should I try to build ANGLE tool from https://github.com/google/angle ? |
|
Hi!
The appropriate steps for compiling qt5-base using VS2019 are:
Just don't look at the versions of postgres or openssl being built... I added the instructions above for you because they work here for me. I was building Qt this weekend. Edit: Problems compiling the version of ANGLE shipped with Qt indicate a problem with the Windows SDK installation. Check that you have it installed via the individual components section of the Visual Studio installer. ANGLE is used by Qt to convert opengl calls into DirectX. On Windows 10, it uses the DXSDK shipped with the Windows 10 SDK to do so. |
Jimmy-Hu
changed the title
|
@heydojo Thank you for your detailed reply.
|
|
Honestly, you just delete the triplets and it will build (but then debug is built too.) Or you can wrap the debug only code in a conditional as demonstrated in #6857.
You're very welcome. I'm glad I could help. |
|
@Jimmy-Hu, thanks for posting this issue! However, I installed qt5-base[core]:x86-windows and qt5-base:x64-windows successfully with latest vcpkg and VS2019 16.2 preview 2.0. Noted that has a bug in qt5-declarative when you only build with Release configuration, currently this issue fixed, see linked PR #6972 above. Could you pull master and try again? x86 Total elapsed time: 2.914 h The package qt5-base:x86-windows provides CMake targets: |
@PhoebeHui Thank you for your reply. |
|
@Jimmy-Hu It seems that your installation port zlib/doubleconversion/pcre2/libjpeg-turbo has some problems, please rebuild them before building qt5-base. |
|
I have same error as in first post - fresh windows 7 virtual machine with latest vcpkg, called "vcpkg install qt5-base:x86-windows", using visual studio 2015 with latest patches. After fail called "vcpkg install qt5-base", did not work. |
|
Qt5 has been updated to 5.12.5, this issue may have been fixed. Thanks. |
|
@JackBoosY The content of file "D:\GitHub\vcpkg\buildtrees\qt5-base\config-x64-windows-dbg-out.log" is as https://gist.github.com/Jimmy-Hu/e9647240e9d986bc25cb55fab80d1833, and the content of file "D:\GitHub\vcpkg\buildtrees\qt5-base\config-x64-windows-dbg-err.log" is as https://gist.github.com/Jimmy-Hu/4d3e306cc8e10272c4aa08adb0cfb906 Is there any way to fix it? |
|
@Neumann-A Any ideas? |
|
@JackBoosY: Some error finding the mkspec. Not enough information with this log. Needs vcpkg/ports/qt5-base/portfile.cmake Line 64 in 67a9305 and repost the log. Their is also be a config.log in the x64-windows-dbg buildtree folder which is also required to further debug this issue.
|
|
@Neumann-A Thank you for giving some instructions to help me dealing with this problem. The content of file "D:\GitHub\vcpkg\buildtrees\qt5-base\config-x64-windows-dbg-err.log" is as https://gist.github.com/Jimmy-Hu/0bac9219af0294e2b6c0396d2485fb18 , and the content of file "D:\GitHub\vcpkg\buildtrees\qt5-base\config-x64-windows-dbg-out.log" is as |
|
I don't now if you solved the problem yourself in the meantime but the line should give enough information/context why it fails. should all be found. So either you messed up your debug/lib folder somehow or something strange is happening. |
|
@Neumann-A Sorry for late update. I re-cloned the repository from https://github.com/microsoft/vcpkg and followed quick start to setup the environment. Then tried to reinstall qt5. It turns out that openssl-windows:x64-windows install error. Furthermore, I also tried to run individual command to install openssl-windows:x64-windows package. |
|
Real problem is: delete the file and try again. The file was probably corrupted somehow or you ran out of disk space. (Perl is quite large) |
|
@Neumann-A Thank you for your prompt reply. |
That was the purpose of deleting that file. Did the build then proceed or did it fail again with the same error? |
|
After the download process, the same error happened again. |
|
Seems like there is something wrong with your network, so I downloaded corrupted packages. |
|
@JackBoosY I wonder that the SHA-256 of the completed file "trawberry-perl-5.30.0.1-32bit.zip". |
|
@JackBoosY After downloaded multiple times, it's weird that I found the SHA-512 of my downloaded "trawberry-perl-5.30.0.1-32bit.zip" is also I use HashMyFiles to get these checksum. Does anyone has the same situation? |
|
@Jimmy-Hu Can you remove cmake you installed and try again? May be it's a cmake bug. |
|
@JackBoosY Thank you for your reply. I downloaded the cmake "Windows win64-x64 Installer" from https://cmake.org/download/. Cmake version is 3.16.2 now.
Then, the problem is as same as above. 🤔 |
|
File I:/vcpkg/buildtrees/openssl-windows/src/openssl-1-c41872ef97/apps/rand.c should be exists, this issue is indeed a cmake extraction bug. And I guess you can use #8112 (comment) workaround to fix this issue now. |
|
@JackBoosY Thank you so much for providing useful links. I noticed that the format of disk which I cloned vcpkg repository in is exactly exFAT, and I moved vcpkg folder to another disk which is NTFS format. Then, re-run quick start to setup the environment and try to install openssl package. I am glad that the installation finished successfully. It seems that cmake had some problem in unzip file in exFAT disk. Next step, I try to run the command Finally, I ran the command Happy to close the issue, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The error message as shown as below.
OS and Visual Studio version:
Windows 10 Home 1903, Visual Studio 2019 Version 16.1.2
Does anyone has the same problem?
The text was updated successfully, but these errors were encountered: