Installation and Deployment

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.

having issues reaching https://code.qt.io/yocto/meta-qt6 myself. tried a mirror but then like 8 tasks in my kas build fail trying to build recipes in there that try to pill from code.qt.io. be nice if someone could confirm the issue and that they are working on it or tell us we are crazy and it's not down and it is just our systems that are screwed up

https://www.qt.io/blog/extended-security-maintenance-for-qt-5.15-begins-may-2025 Try the archive choice in the Show combo box.

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.

I think jom has a problem with the makefile. Although not a root cause, as per the advice I disabled jom and the problem went away: [image: abf6b98f-23f8-4691-ae16-f60ad4c5b28c.png]

I found this cryptic error means there is a prerequsitie: Ensure that "Desktop development with C++" workload is installed in MSVSC: [image: d2f2fef4-5df3-4b17-a844-2ec1964ad739.png] After reinstalling the Qt extension, it no longer complains. Furthermore: Run Qt MaintenanceTool.exe and ensure MSVC 2022 option is installed: [image: f675868a-8ebb-4b3b-82e5-80abe8a3a0de.png] When prompted in MSVSC, hit Import and browse to C:\Qt\6.9.3\msvc2022.. [image: d8e657c7-fd2f-45e6-9764-c2bd95f33b00.png]

After many tries I tracked it down to the type of configuration if I use debug-release, which creates a Ninja Multiconfig project, it fails with this error. but if I build debug and release version is separated directories it works fine. hopefully this finding will help others.

Ok, got to use a newer version of the image I ran this on, it worked fine with 17.9.3. Thank you very much for the quick answer!

@DkjL Below you have a recording from a Qt 6.10 installation on Windows 11 from 0 to hero. https://bugreports.qt.io/secure/attachment/179728/qt6.10-qtcreator-installation.mp4 I've installed: Qt 6.10 for MSVC 2022, MinGW 13.1.0, LLVM MinGW 17.0.6 CMake and Ninja MinGW 13.1.0 and LLVM MinGW 17.0.6 toolchains [image: 75deba54-cda7-4ea1-9ca1-2eafc9fc0a53.png] And then I've picked up an example an compiled with all three compilers.

@vedansh said in Qt ain't detecting MSVC compiler: u mean after installation with current configuration, i manually select msvc ? This doesn't work. Libraries compiled with MinGW cannot be used with MSVC. You need to specifically install the Qt libraries for MSVC and not the ones for MinGW. This has nothing to do with compiler detection. There is no compiler detection at installation time (only within QtCreator). Select what you want, i.e. Qt libraries for MSVC, manually during installation. Don't install the libraries for MinGW and certainly don't install MinGW itself if you don't want to use it.