Installation and Deployment

@jsulm Hi...thanks for staying with this... So the hidden or "greyed-out" Kits that I referred to are regarded as "unsuitable" Kits by Qt Creator, and they cannot be selected by the end user. If I did not take the step of unchecking the "Hide unsuitable kits" checkbox, then no Kits would display at all. So I cannot check the details about the grayed-out items shown, or see errors/warnings about why they are "unsuitable" (to my knowledge). This is illustrated in the photo below: [image: 0124ebf7-00f1-4ac3-993a-3023f199bff7.png]

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

@JKSH Thank you!

thanks for the suggestion. switching to cmake 3.22.6, which is the minimum recommended, I get the same problem exactly. I even tried the 6.9.2 branch from git, but got the same result. I will be having a go with 6.10 RC to see if I have the same issue.

Ok thank you

@SGaist said in ./configure troubles in mac: Wiki page Thanks for sharing, it's worth taking a look for me! (I see the TB I have haha)

@Axel-Spoerl Thank you, yes I needed to compile Qt by myself. This solved my Problem: source /home/emmynoether/emsdk/emsdk_env.sh mkdir -p $HOME/qt-build && cd $HOME/qt-build export QT_HOST_PATH=$HOME/Qt/6.8.3/gcc_64 git clone --depth 1 --branch v6.8.3 https://code.qt.io/qt/qt5.git qt6-src cd qt6-src # I catched all submodules git submodule sync git submodule update --init --recursive ./configure \ -xplatform wasm-emscripten \ -prefix $HOME/Qt/6.8.3/wasm_singlethread \ -opensource -confirm-license \ -nomake tests -nomake examples \ -skip qtwebengine \ -qt-zlib \ -release \ -opengl es2 cmake --build . --parallel $(nproc) cmake --install . And in the CMake I added Qt6::BundledZLIB to target_link_libraries. At the end it worked to use CLion.

Thanks for the reply @Christian-Ehrlicher , may be dump question , can we install the installer that you have shared for arm64 installer(https://download.qt.io/official_releases/online_installers/) on the podman container directly ? on top of that can we customize the other lib like openssl,icu versions is it possible ?

@Christian-Ehrlicher is there any pre-requistic for hardware to do cross compile for the host device ...

@MT34 said in Product type is not an application, not building an APK.: 13:05:09: Product type is not an application, not building an APK. I know nothing, but try see whether https://forum.qt.io/topic/162329/qtcreator-15-changing-android-application-name-breaks-build helps? Or general "delete what you have and have a go again from scratch"?

Hi, I think you should bring that question to the interest mailing list. You will find there Qt's developers/maintainers. This forum is more user oriented.

If you are using the Qt Maintenance Tool or the Qt Online Installer and only see Qt 6.x (for example Qt 6.9), you can still install older versions like Qt 5.15.x. By default, the installer hides archived versions. To enable them: Open the Qt Maintenance Tool (or run the Online Installer). Log in with your Qt account. On the “Select Components” page, look for the filter options at the top. Enable the “Archive” option. Now you will see older releases, including Qt 5.x.x versions. Select the version you want (e.g. Qt 5.15.2) and install it. This way you don’t need to manually download and build from source — the installer can fetch the archived packages for you.