building qt: qtdeclarative:x64-windows failed with build failure #30446
Comments
breazyyrn
added
the
category:port-bug
|
Please use the autogenerated issue body mentioned in the console. |
|
Probably same issue as always with qtdeclarative. Build paths are too long. Use |
|
ربما نفس المشكلة كما هو الحال دائما مع qtdeclarative. بناء المسارات طويلة جدا. استخدم (في وضع البيان الذي تم تمريره عبر --x-buildtrees-root=<some_short_path>VCPKG_INSTALL_OPTIONS) |
LilyWangLL
added
requires:more-information
|
Please provide the error log. |
|
@breazyyrn @Talaqalotaibipmp, could you please provide the full failure logs? |
|
I also encountered a build error with qtdeclarative and here is the accompanying information: Host Environment
To Reproduce
Failure logs C:\Users\ctxuser\Documents\vcpkg\buildtrees\qtdeclarative\install-x64-windows-dbg-out.logAdditional context which seems like the underlying error. Please let me know if you need any additional information. |
|
again #30446 (comment)
|
|
Sorry for the late response guys! Been very busy this past week. Although, I'm very happy to say that I fixed the problem using GPT-4's help lol. Instead of windows, I just built Bitcoin Core all over again using Ubuntu and I had no troubles at all. Just had a lot of problems in regards to dependencies when trying to build on windows, was a task that took me over a week to navigate but it only took me a day with Ubuntu and everything is running perfectly now. Thank you all for your help! |
|
If you do have access to ChatGPT plus and GPT-4 option that is provided once subscribed, and you are interested in building, I suggest using this prompt (remember on GPT-4), replace my username and names with yours, and replace the directories to your correct directories, let me know if it works. If you don't have access to GPT-4 try it on regular ChatGPT if it doesn't work I'll happily provide you with what I get when I input the prompt on my computer. Please note that on this prompt I clearly mentioned that I already had the vcpkg, sudo and automake folders since I tried building it before, but don't think you need them with this implementation anyways. Here's the Prompt I kept: I'm working on building the Bitcoin Repository, I've tried it before but due to some errors I have to start it again, this time I downloaded it into my external storage to be efficient with the storage which I have. My directory now is: D:\Bitcoin ...here are the build instructions from github, i already have vcpkg since I have worked on it before so I had saved it in a file earlier, I also have automake on the file: Skip to content @breazyyrn WINDOWS BUILD NOTES The options known to work for building Bitcoin Core on Windows are: On Linux, using the Mingw-w64 cross compiler tool chain. On Windows, using a POSIX compatibility layer application such as cygwin or msys2. Cross-compilation for Ubuntu and Windows Subsystem for Linux First, install the general dependencies: sudo apt update See dependencies.md for a complete overview. If you want to build the windows installer with make deploy you need NSIS: sudo apt install nsis git clone https://github.com/bitcoin/bitcoin.git on modern systems (Ubuntu 21.04 Hirsute Hippo or newer, Debian 11 Bullseye or newer): Note that for WSL the Bitcoin Core source path MUST be somewhere in the default mount file system, for example /usr/src/bitcoin, AND not under /mnt/d/. If this is not the case the dependency autoconf scripts will fail. This means you cannot use a directory that is located directly on the host Windows file system to perform the build. Additional WSL Note: WSL support for launching Win32 applications results in Autoconf configure scripts being able to execute Windows Portable Executable files. This can cause unexpected behaviour during the build, such as Win32 error dialogs for missing libraries. The recommended approach is to temporarily disable WSL support for Win32 applications. Build using: PATH=$(echo "$PATH" | sed -e 's/:/mnt.*//g') # strip out problematic Windows %PATH% imported var Installation make install DESTDIR=/mnt/c/workspace/bitcoin make deploy |
@Neumann-A That's odd though, because I (think I) have enabled long paths for my Windows installation, so I assumed this problem shouldn't occur? |
|
Long path support means nothing if the tools dont enable it via the manifest and they dont. |
|
Meh. Anyway, thanks for your help - moving vcpkg to |
LilyWangLL
added
category:question
|
Since this issue has been resolved, I am closing this issue for now. Thanks for everyone's help. |
I used F:/vcpkg, but it still failed. :( |
error: building qtdeclarative:x64-windows failed with: BUILD_FAILED
error: Please ensure you're using the latest port files with
git pullandvcpkg update.Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+qtdeclarative
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[qtdeclarative]+Build+error
Include '[qtdeclarative] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
vcpkg-tool version: 2023-03-14-105f7f7e8a5ea10dfac9874ff9d1a6bacba5f454
vcpkg-scripts version: e249dfb 2023-03-20 (6 days ago)
The text was updated successfully, but these errors were encountered: