Installation and Deployment

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.

@JKSH Thank you!

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