Installation and Deployment

See this Wiki page. There's nothing more to install but yes, starting from the command line is easier.

I'm having problem installing aur/qt5-webengine and aur/qt5-websockets because it can't clone the source. https://code.qt.io/qt/qt-webengine.git i tried both with vpn and no vpn. i can ping, can't load in browser and can't clone. Error from yay package manager: -> Cloning kde-qtwebengine git repo... Cloning into bare repository '/home/parsivan/.cache/yay/qt5-webengine/kde-qtwebengine'... fatal: unable to access 'https://code.qt.io/qt/qtwebengine.git/': Failed to connect to code.qt.io port 443 after 134437 ms: Could not connect to server ==> ERROR: Failure while downloading kde-qtwebengine git repo Aborting... -> error making: qt5-webengine-exit status 1 -> Failed to install the following packages. Manual intervention is required: qt5-webengine - exit status 1

The reason is that GitHub just zips the content of the repository. The official archives are ready to configure/build for the platform selected (.zip for Windows and tar.gz for unix like).

Sometimes you have bugs in one architecture and not the others. It might also just be a subtle difference in you settings, etc.

@Christian-Ehrlicher Ok, I got it. I will look into the source code and try to fix the warnings.

@Mucip said in Library problem: libxcb-cursor0 libxcb-cursor-dev: I applied below code and result. But in this case error message did not appeared?! The installer itself does not need libxcb-cursor. It was trying to warn you that your Qt-based projects might not be able to find it. I don't know why you might get that warning message if you've already installed the libraries. But as @JonB suggests, you might not need libxcb-cursor anyway since your system is using Wayland.

@akshaybabloo From the page you linked: "To get the Qt essentials package content with, for example, the MSVC 2022 binaries, use the corresponding qt6.10.0-msvc2022-essentials alias package."

solved i reset my password from qt installer

@new_ said in QT online installer v5-15 not available: qt5.15.16 is not download？ No, it is only provided as source code: https://lists.qt-project.org/pipermail/announce/2025-October/000592.html (Note also that Qt 5.15.18 has been released under open-source licenses)

I face the same issue. Did you create an Qt Bug? I skipped the SBOM generation with -DQT_GENERATE_SBOM=OFF

@major_tom3 hi, That's surprising that you have to create that symlink manually. Usually the package manager does that for you on installation.

Encountered this same issue on x86_64 with Qt6.8 (from Conan) with the following settings: [settings] arch=x86_64 compiler=gcc compiler.libcxx=libstdc++11 os=Linux compiler.version=11 compiler.cppstd=23 OpenGL dev package is already installed via: sudo apt-get install build-essential libgl1-mesa-dev

So, my problem was that Mesa installed from repository and it was fixed by adding -no-sbom in configure

@JonB said in deploying from Visual Studio - options to windeployqt: He is saying there is an option to windeployqt I was still asleep :) qt_generate_deploy_app_script() takes DEPLOY_TOOL_OPTIONS where you can pass it. If there is an ui element in the VS Addin - don't know, don't use this.

Because the maintenance tool only show modules for the latest supported releases and preview by default (+ your already installed modules). You need to enable the Archive category to view older module. In my maintenance tool it's in a Category tab on the right, in yours maybe it's in the "Show" combo box.

I had the same problem when I was trying to debug my app and gdb stopped responding, so I closed QtCreator (version 17.0.2) and apparently instead of properly closing and writing its settings as it usually does, it crashed and botched some file(s). After opening QtCreator again both system CMake (I'm on Linux Mint 22.2) and qt-bundled one were showing "version not parseable". Running qtcreator -temporarycleansettings as was suggested above didn't have this issue. So in my case the issue apparently was caused by ~/.config/QtProject/QtCreator.ini inside which there was a section [%General] DefaultFileEncoding=@ByteArray(UTF-8) DefaultLineTerminator=1 LastPreferencePage=K.CMake.Tools OverrideCodecForLocale=@ByteArray(037) OverrideLanguage=C SortCategories=false After I removed this section and opened QtCreator again, everything was fine. So I guess this incorrect section somehow messed with QtCreator parsing its .ini Also interesting that along with this incorrect section there was also normal correct [General] section, and it had no keys/values like the incorrect one.