Installation and Deployment

@dondioci I build the qt installer framework is the same error ?

I'm sorry, but it's been too long ago. There have been so many changes in Qt since then, it very well may work now, but my procedure works correctly, so I haven't been motivated to experiment.

In fact, I don't think I'm even using github for my Qt source files any longer, but am obtaining them through the Qt maintenance tool. So, there are alternatives to my method.

When I selected such a Device:
android9.png
, the program almost started.
There was nothing in the Problems window.
But in the Output window there were warnings and errors:
output1.png
output2.png
.
And the program still did not start:

Oh, yes, I've forgotten that.

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

I don’t know, the log doesn’t say that. When you try to compile Qt on an unsupported platform, you’re on your own. Slackware is particularly problematic, because it doesn’t resolve dependencies automatically.

Since Qt fails compiling the Chromium 3rd party module, you could try whether there is a tutorial how to compile chromium on its own for Slackware and which packages are required for that. It would at least solve this problem. Can’t guarantee, that another problem will occur once QtWebengine works.

Well, I was able to build QT6 6.8.2 without QtWebEngine, and the most of my projects working very well, but there is a issue with qt5compat.

[ 1%] Generating ../../lib64/qt6/mkspecs/modules/qt_lib_core5compat_private.pri [ 1%] Built target Core5Compat_lib_pri [ 2%] Running syncqt.cpp for module: QtCore5Compat [ 2%] Generating version linker script for target Core5Compat [ 2%] Built target Core5Compat_version_script [ 3%] Built target Core5Compat_sync_headers [ 3%] Built target Core5Compat_autogen_timestamp_deps [ 3%] Automatic MOC for target Core5Compat [ 3%] Built target Core5Compat_autogen [ 4%] Generating prl file for target Core5Compat [ 5%] Generating pc file for target Qt6::Core5Compat [ 5%] Running AUTOMOC file extraction for target Core5Compat [ 5%] Running moc --collect-json for target Core5Compat [ 6%] Building CXX object src/core5/CMakeFiles/Core5Compat.dir/Core5Compat_autogen/mocs_compilation.cpp.o c++: error: unrecognized command-line option ‘-ftrivial-auto-var-init=pattern’ gmake[2]: *** [src/core5/CMakeFiles/Core5Compat.dir/build.make:99: src/core5/CMakeFiles/Core5Compat.dir/Core5Compat_autogen/mocs_compilation.cpp.o] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:1331: src/core5/CMakeFiles/Core5Compat.dir/all] Error 2 gmake: *** [Makefile:146: all] Error 2

You can choose how to use the openssl libs: https://doc.qt.io/qt-6/configure-options.html#ssl

ahhhhhh, now the fog in my head clears up slowly, Thanks!

OK, I'll try now.
Thanks.

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.

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

Let's take one step back.
This is a forum, where volunteers help each other for free.
If you have an issue and you communicate with someone, the rule is to provide as much information as possible.
Example; I asked if you have other drives on your PC.
=> "Yes" is the wrong answer. It doesn't help, it just wastes your time and mine.
=> The right answer is to tell exactly which drives you have. Since we are searching for a file, it may be a good idea that you copy the search command and start searching by yourself. A little co-operation is better than expecting to told every step.

To your problem:
As said before, you have selected to update Qt Creator. You have not selected a new installation.
The installer has found Qt Creator 16.0.0, so it is on your PC.
If you don't find it, there is something wrong on your PC that occurred after the installation.
Maybe, as said before, a virus scanner has quarantined the executable.
But you have to check that yourself with your virus scanner.
The problem has nothing to do with Qt.

@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 ?