How to set icon for Qt Android app in CMake?

Akshai

@SGaist Latest one.

SGaist

That's Qt Creator. I am asking which version you use to build your application.

Akshai

@SGaist This one.

SGaist

So you put your Androïd related changes in the else clause that concerns Qt 5.

Akshai

@SGaist What to do? please guide me.

SGaist

Move your changes to the Qt 6 part of the if.

Akshai

@SGaist Done as mentioned. But there is no change found. Please see screenshot.

sierdzio

Remember to do a full rebuild (clean, run cmake, rebuild) when you change cmake code.

J.Hilk

@Akshai also, delete the app from your device, let it install fresh

Akshai

@sierdzio @J-Hilk I have done as you guys mentioned. Couldn't found any change.

Fest

I have exactly same problem. Can't set icon and force portrait mode.
AndroidManifest.xml from android directory and from build directory not same.

Qt 6.4, QtCreator 8.0.2

TomZ

I just yesterday figured this out for my app.

I use QT_ANDROID_PACKAGE_SOURCE_DIR instead.
See the full CMake snippet here;

    set_target_properties(pay_mobile PROPERTIES
       QT_ANDROID_PACKAGE_SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/android
   )

The XML file is in my subdir 'android' (as the above shows). It includes the property android:icon="@drawable/icon"
Example here.
In that same 'android' directory there is a `res/drawable' set of directories which contain the icons with the 'icon' base for the filename. Both of those you can see reflected in the above point. link.

Hope that helps!

Fest

@TomZ Thank you !
Adding this solved the issue ! Now everything works like a charm.

if (ANDROID)
    set_target_properties(${PROJECT_NAME} PROPERTIES
        QT_ANDROID_PACKAGE_SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/android
    )
    qt6_android_generate_deployment_settings(${PROJECT_NAME})
    qt_android_add_apk_target(${PROJECT_NAME})
endif ()

Akshai

@TomZ Thank you !!!
Added below line. This solved my issue.

Luis Miguel

@Fest I would honestly love to understand how you came up with that. I'm still too new to understand what's going on in CMakeLists.