Installation and Deployment

@deleted28 said in [solved] Installer certificate problem:

mcosta,

Yes, found it - not too blind but too stupid :)
thank you

Don't worry, i tried to click "Logout" on the image...

In my case, changing to a local installer copy worked fine..
Really strange since both have the same size, same version...

Ultimately there are many developing tools that are behaving so randomly, including Visual Studio..
I think machine are getting closer to humankind..

I am writing these posts from my Mac, on which I am actively programming with Qt and never ever have I had the need to sign anything that I run from Qt Creator, also no need for deployment steps. If, however, you run standalone app package - yes, you need to do both.
I am unable to say how does CLion come into the equation as I never used it.

For the sake of completeness, you could also build the Linguist tools separatey, e.g. for Qt 6.7.3 like this:

Get the sources:

wget https://download.qt.io/official_releases/qt/6.7/6.7.3/submodules/qttools-everywhere-src-6.7.3.tar.xz tar -xvf qttools-everywhere-src-6.7.3.tar.xz mkdir qttools-everywhere-src-6.7.3/build cd qttools-everywhere-src-6.7.3/build

Then build the Linuist tools:

cmake -G Ninja \ -DCMAKE_PREFIX_PATH=~/Qt/6.7.3 \ -DCMAKE_INSTALL_PREFIX=~/Qt/6.7.3 \ -DFEATURE_assistant=OFF \ -DFEATURE_clang=OFF \ -DFEATURE_designer=OFF \ -DFEATURE_pixeltool=OFF \ -DFEATURE_qdbus=OFF \ -DFEATURE_qtattributionsscanner=OFF \ -DFEATURE_qtdiag=OFF \ -DFEATURE_qtplugininfo=OFF \ .. cmake --build . --parallel cmake --install .

@jsulm You mean I should replace corresponding folders from qt official by folders from crystal's qt 6 build project?

I think all that matters is your Qt Account. If you don't have any commercial licenses or trial licenses attached, the installer will only show you the FOSS options to install.

Just in case you need it, the download link is: https://www.qt.io/download-qt-installer

I just upload the full log if you need.

Log file: https://filebin.net/e0hlon89mx2qqncy/Qt-5.15.16.log

PS: Thanks for the hint with macdeployqt, but in this case, the packaging is quite easy, as I build using a static Qt. So there's only the binary itself, without having to add external libraries.

@LucasYuen said in Qt Creator (Qt version 6.7.3) interface is garbled:

Linux system version is too old?

Probably.
See https://doc.qt.io/qt-6.7/linux.html

@fulltopic See https://doc.qt.io/qt-5/macos.html#architectures
Qt 5.15 is available as binary for Mac arm64 (via official installer). Just install XCode and Qt and you can build for Apple Silicon.

@SGaist

@SGaist said in How to replace the QT installed by apt-get?:

Hi,

I'd go a step further than @JonB: you just don't.

Trying to replace your system libraries with variants built for development on a larger set of distribution is a no go.

Use the LD_LIBRARY_PATH environment variable to point your application to your custom Qt. Do it in the terminal you use to start that application or in a bash script to start the application.

Do NOT use it to modify which version of Qt is used by your whole system. This will only bring troubles.

Got it.

@SimonSchroeder said in Some doubts about Linux deployment:

@Paul-Colby I didn't know that linuxdeploy had plugins. We are currently using linuxdeploy to create the AppDir and then linuxdeployqt to add the Qt dependencies. However, if I'm not mistaken linuxdeploy also requires an older Linux version. (But, as you can see from my example we also didn't manage to create an AppImage with linuxdeployqt alone.)

Actually, I was able to deploy a working appimage using the three tools above! With the "low-level " approaches I still had problems.

I'm pretty new to these tools, but as far as I understand they can work together as plugins or just as three separate calls. I'm using Ubuntu 24.10 right now so they work on pretty modern systems (I didn't test the appimage on older systems because I don't need to support them).

Hi,
I am also facing the same issue.

@Tchort can you please elaborate your answer.

I tried , reinstalling the host system, and reinstalling rpi. I was able to compile the qt cmake.

Bit I'd like to know the actual reason behind this error

@Perdrix The installer gives you the possibility to select a location to install. By default it is your home folder.

Upper variant works for me as well

I found this (after a bit of digging):

https://forum.qt.io/topic/159779/deployment-on-linux

It answers most of my questions for now. I'll mark this as solved and come back later it I need to.

I have been looking for the same thing, but unfortunately the Qt Company does not seem to offer a documentation on the subject just yet. I had to go through the Qt's source codes, but finally found a solution:

Assuming your host OS is Windows x86_64 and you want to compile Windows arm64 packages for your project.

Install both versions (arm64, x86_64) of Qt and MSVC (make sure you select arm64 packages when you are installing MSVC on Visual Studio Installer; not arm). Compile your project with the following commands (on cmd.exe):cd your_project_folder call "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\Build\vcvarsamd64_arm64.bat" C:\Qt\6.8.0\msvc2022_arm64\bin\qt-cmake.bat -S . -B build-arm64 -G Ninja -DQT_HOST_PATH=C:\Qt\6.8.0\msvc2022_64 -DCMAKE_BUILD_TYPE=Release cmake --build build-arm64 --parallel --config Release

Assuming you are using Ninja as the generator (but you can remove -G Ninja if you don't)

Deploy your project with windeployqt by passing --qtpaths option like below (on cmd.exe):C:\Qt\6.8.0\msvc2022_64\bin\windeployqt.exe --qtpaths "C:\Qt\6.8.0\msvc2022_arm64\bin\qtpaths.bat" ...

So we are using windeployqt.exe from the msvc2022_64 setup, but letting it use the msvc2022_arm64 setup while deploying the dependencies by passing the --qtpaths argument.

I have built my project with that but was not able to test it on an arm64 machine yet, so please let us know if it works.

Edit 1: Apparently this requires that your Qt installation do reside in C:\Qt path. If your Qt installation path is different than that, you may try to circumvent this problem by editing out the paths listed in ...msvc2022_arm64\bin\target_qt.conf file.

Edit 2: There seems to be a bug in the Qt 6.8.0 win64_msvc2022_arm64_cross_compiled setup (i.e., I realized it when I installed it via the aqtinstall tool on my CI machine; but there was no such bug when I installed the same Qt setup to my personal computer using official Qt installation tool a few days back.) Make sure the path to your x64 setup inside the C:\Qt\6.8.0\msvc2022_arm64\bin\qtpaths.bat file is correct (edit the bat file if it contains the wrong path due to the bug I just mentioned).

Hope it helps.