Installation and Deployment

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.

cmake_minimum_required(VERSION 3.16) project(PhotoStdAesthetic VERSION 0.1 LANGUAGES CXX) set(CMAKE_CXX_STANDARD 17) set(CMAKE_CXX_STANDARD_REQUIRED ON) set(CMAKE_AUTOMOC ON) set(CMAKE_AUTORCC ON) set(CMAKE_AUTOUIC ON) set(CMAKE_INCLUDE_CURRENT_DIR ON) Qt paketleri (Sql'i açtım, gerekirse yorumla) find_package(Qt6 6.9 REQUIRED COMPONENTS Core Gui Quick Multimedia QuickControls2) qt_standard_project_setup(REQUIRES 6.5) Ana executable (Android’de otomatik .so üretir) qt_add_executable(appPhotoStdAesthetic main.cpp src/Camera/CameraHandler.cpp src/Camera/CameraHandler.h src/Share/ShareUtils.cpp src/Share/ShareUtils.h src/UserModel/UserModel.cpp src/UserModel/UserModel.h src/GalleryModel/GalleryModel.cpp src/GalleryModel/GalleryModel.h ) qt_add_qml_module(appPhotoStdAesthetic URI PhotoStdAesthetic VERSION 1.0 QML_FILES Main.qml qml/Pages/PageUserPro.qml qml/Pages/homePage.qml qml/Pages/CamPageNose.qml qml/Pages/PageGallery.qml qml/Pages/PageViewer.qml qml/Pages/PageRegister.qml qml/Components/ButtonCustom.qml qml/Components/DelegateThumbnail.qml qml/Components/ItemUserPro.qml RESOURCES assets/images/home_grid1.png assets/images/home_grid2.png assets/images/home_grid3.png assets/images/home_grid4.png ) Android ayarları if(ANDROID) # Android deploy dizini ve hedef ABIs set_target_properties(appPhotoStdAesthetic PROPERTIES QT_ANDROID_PACKAGE_SOURCE_DIR "${CMAKE_CURRENT_SOURCE_DIR}/android" QT_ANDROID_ABIS "arm64-v8a" QT_ANDROID_PACKAGE_NAME "com.photostdaesthetic.app" QT_ANDROID_TARGET_SDK_VERSION 34 ) # Plugin import: Debug ve Release için ayrı ayrı veya ortak qt_import_plugins(appPhotoStdAesthetic INCLUDE_BY_TYPE imageformats EXCLUDE_BY_TYPE qmltooling EXCLUDE_BY_TYPE iconengines EXCLUDE_BY_TYPE networkinformation EXCLUDE_BY_TYPE tls EXCLUDE_BY_TYPE platforminputcontexts ) # Deploy script oluştur ve yükle qt_generate_deploy_qml_app_script( TARGET appPhotoStdAesthetic OUTPUT_SCRIPT deploy_script NO_UNSUPPORTED_PLATFORM_ERROR DEPLOY_USER_QML_MODULES_ON_UNSUPPORTED_PLATFORM ) install(SCRIPT ${deploy_script}) endif() Masaüstü ayarları if(NOT ANDROID) set_target_properties(appPhotoStdAesthetic PROPERTIES MACOSX_BUNDLE_BUNDLE_VERSION ${PROJECT_VERSION} MACOSX_BUNDLE_SHORT_VERSION_STRING ${PROJECT_VERSION_MAJOR}.${PROJECT_VERSION_MINOR} MACOSX_BUNDLE TRUE WIN32_EXECUTABLE TRUE ) endif() Qt kütüphaneleri target_link_libraries(appPhotoStdAesthetic PRIVATE Qt6::Core Qt6::Gui Qt6::Quick Qt6::QuickControls2 Qt6::Multimedia )

In the error message you can see why it fails to link. You can also simply ignore this submodule with -skip option from ./configure

Sorry for not posting before, but I had completely forgotten about this thread!!! The problem is not happening lately; now I'm using Qt Creator 17.0.0 and the latest (as of today) version of MSVC 2022. However, the last times this problem happened I could solved more or less quickly following the steps below: Go to folder %appdata%\roaming. Here, delete subfolder QtProject Still in %appdata%\roaming... I'm not sure about whether deleting subfolder Qt is necessary, since it contains your credentials to log into the Qt websites. Normally, I delete it and when finishing the process I retype the credentials once more. Then go to folder %appdata%\local. Then delete subfolder QtProject. Then go to folder %appdata%\Temp and there delete all files whose name start with "QtCreator-" (there will be quite a few!) Finally, using the Qt Maintenance Tool, uninstall Qt Creator. Once that it's been completely uninstalled, reinstall it again. As I said, this worked for me the last two or three times the problem arised. Can't guarantee that it'll work for everybody! I guess that deleting the files and folder listed above I'm cleaning all traces pointing to MSVC. Uninstalling and reinstalling forces re-creating (hopefully) correctly these links.

I seems that updating the conf via rcc update maintenancetool.dat but keep the old maintenancetool.ini and the ini file still contains the old repo.

Shot in the dark, but you might try a slightly older CMake version. Just suggesting this as CMake 4.1.1 is fairly new, and the error message looks ... dubious.

Hi and welcome to devnet, If memory serves well you can use -I /path/to/include.