Installation and Deployment

@Axel-Spoerl said in Failing to build Qt 6.7.3 from source on Slackware 15.0:

Hi,
QtWebEngine doesn't compile because of some dependency mismatch.

Which dependencies?

Hi,

One thing to do is use a tool such as Dependency Walker to ensure you have all the dependencies of your application in place. Which means also checking the dll/plugins of your dependencies.

Has this problem been solved? I also encountered the same problem. The CMake settings show that the CMake version cannot be parsed. I have tried reinstalling qt, qt creator and cmake, but none of them worked.

@Micha-Sett said in Where to find silicon MAC Version of open source for QT Designer:

And WHERE exactly is the open source version for qt

In the link I gave you - just scroll a bit down...

I opened a support ticket from my account, and they terminated the license. I was able to install the LGPL version.

thank you mr
yes, you are right

Seems like due to this bugs discussions(specifically messages from Katja Marttila)
https://bugreports.qt.io/browse/QTIFW-3180
https://bugreports.qt.io/browse/QTIFW-2611

It's required to build QT statically for installer despite the fact that it's recommendation in instruction.

@Kors Try another mirror. See https://wiki.qt.io/Online_Installer_4.x

Maybe it will help someone else. Personally, adding the "QmlDesigner" extension helped me.

MSYS2 Qt is another idea, which provides all-in-one POSIX-like pacman packages , not only Qt 5/6 Included, but also libboost\opencv\gdal\fftw. The only problem is Web Engine does not support mingw64,. in MSYS2 you can fallback to a fresh version of WebKit.

This issue isn't related to Qt.
Contact your internet provider or your network admin to fix it.

Also supporting @SGaist's reply, for GitHub Actions, I use the install-qt-action action quite a lot. Here's a bit of an extreme example of a project of mine that builds on GitHub Actions for all latest Qt minor releases from Qt 5.9 to 6.9 Beta 2, on Linux, Windows and macOS (skipping Qt 6.0 and 6.1 though, just because they don't support Bluetooth, which that project uses), with gcc, clang, msvc and mingw, for x86, x86-64 and arm64 (currently 146 different bulds) : https://github.com/pcolby/dokit/blob/main/.github/workflows/build.yaml

More than happy to try to answer any questions you might have about Qt on GitHub Actions, since I've had to figure out a lot of the corner cases the hard way! But most of my learnings are covered in the comments in that build.yaml file :)

Cheers.

You mean manually copy assistant .exe from the Qt install dir to the application build directory and then qt deploy - surely there must be a more formal method than that

D.

@Tom-asso
As @jsulm says. Do you want to examine why you need to set LD_LIBRARY_PATH, you ought not need to?

Hi and welcome to devnet,

Did you already try with a different mirror ?

Hi and welcome to devnet,

Did check for error messages in the kit settings ?

As for the size, it depends a lot on what you selected. What do you have currently ? Beside multiple versions of Qt, are you installing multiple architectures ?

Found the file after quite a bit of digging.

include(/Users/amonra/.vs/DSS/out/build/.qt/QtDeploySupport.cmake) include("${CMAKE_CURRENT_LIST_DIR}/DeepSkyStacker-plugins.cmake" OPTIONAL) set(__QT_DEPLOY_I18N_CATALOGS "qtbase") qt_deploy_runtime_dependencies( EXECUTABLE "/Users/amonra/.vs/DSS/out/build/DeepSkyStacker/DeepSkyStacker.app" DEPLOY_TOOL_OPTIONS -hardened-runtime )

I have already resolved the issue and successfully cross-compiled for arm64 on Ubuntu 24.04 x86 using Qt6.8.2.

I will provide my method.
The configure command is as follows:

../Src/configure \ -prefix /home/ptc/Qt/6.8.2/arm64 \ -qt-host-path /home/ptc/Qt/6.8.2/gcc_64 \ -platform linux-g++ \ -device linux-aarch64-gnu-g++ \ -device-option CROSS_COMPILE=aarch64-linux-gnu- \ -no-opengl \ -skip qtopcua -skip qtwebengine -skip qtwebview -skip qtserialport -skip qtlocation \ -no-feature-brotli -no-feature-hunspell \ -- -DCMAKE_TOOLCHAIN_FILE=$HOME/Qt/6.8.2/toolchain/arm64-toolchain.cmake

Before this, create a new toolchain.cmake file yourself.

set(CMAKE_SYSTEM_NAME Linux) set(CMAKE_SYSTEM_PROCESSOR aarch64) set(CMAKE_C_COMPILER "/usr/bin/aarch64-linux-gnu-gcc") set(CMAKE_CXX_COMPILER "/usr/bin/aarch64-linux-gnu-g++") set(CMAKE_LINKER "/usr/bin/aarch64-linux-gnu-ld") set(CMAKE_AR "/usr/bin/aarch64-linux-gnu-ar") set(CMAKE_FIND_ROOT_PATH /usr/aarch64-linux-gnu) set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER) set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY) set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY) set(CMAKE_FIND_ROOT_PATH_MODE_PACKAGE ONLY)

Next, you can follow my method to add the arm64-related dependencies on x86.

$ sudo dpkg --add-architecture arm64 $ sudo vim /etc/apt/sources.list.d/ubuntu-arm64.sources Types: deb URIs: http://ports.ubuntu.com/ubuntu-ports/ Suites: noble noble-updates noble-security Components: main restricted universe multiverse Architectures: arm64 Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg $ sudo apt update $ sudo apt install -y libudev-dev:arm64 libmtdev-dev:arm64

Finally, execute the configure command.

Same problem here, running Qt Creator 15.0.1 on windows 11