Mobile and Embedded

https://www.youtube.com/watch?v=m7etOQfrMiM

This exact issue haven't solved yet. But found solution to run Swift-CPP interoperability in iOS application with Qt 6 and CMake - it's using static library developed in XCode project where interoperability functionality switched on: -- Create static library for iOS and choose base language Objective-C in settings -- When project created delete all of Objective-C templates -- Switch on C++/Objective-C functionality in build settings -- Add Swift and C++ code, if needed embed all used frameworks -- Build *.a for any platform you need -- Add to Qt 6 CMake project with includes Code samples published here https://github.com/ArboreusSystems/arboreus_examples/tree/master/qt6/CMake/UsingCPPSwiftInterop/UsingCPPSwiftInterop_v2 The recorded video of this sample here https://youtu.be/dZOchNsASHA Happy coding everyone!

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

Hi, I was able to change the NDK root and it compiled all the way till the Generating Android Package step. The next issue i think is a gradle version mismatch. I have the latest gradle version installed and on my system path, but it downloads 5.6.4 during the build and uses that I think which is not compatible with JDK 17: [image: 2de3ed71-c12a-4618-aa8a-53a643fbb7a6.png] [image: c06861ab-255a-425c-8b27-fefb96f21562.png] Any workarounds to that would be highly appreciated

This is a known issue with Qt 6.8.1 Here's the issue in the Qt Bugtracker The comments describe a workaround: copy the androiddeployqt binary from Qt 6.8.0 to the appropriate folder for Qt 6.8.1

I've found the solution! (Qt doc is wrong) set_target_properties(SamsungRC PROPERTIES QT_ANDROID_EXTRA_LIBS "${CMAKE_CURRENT_SOURCE_DIR}/ssl/android/${ANDROID_ABI}/libcrypto_3.so;${CMAKE_CURRENT_SOURCE_DIR}/ssl/android/${ANDROID_ABI}/libssl_3.so" ) The values in QT_ANDROID_EXTRA_LIBS need to be separated by a semicolon.

Have you set the target SDK level and build tools? I have this for my app targeting API level 34 set_target_properties(appskywalker PROPERTIES QT_ANDROID_PACKAGE_SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/android QT_ANDROID_TARGET_SDK_VERSION 34 QT_ANDROID_SDK_BUILD_TOOLS_REVISION 34.0.0 QT_ANDROID_VERSION_NAME ${APP_VERSION} QT_ANDROID_VERSION_CODE ${VERSION_CODE})

I use ApplcationWindow instead of Window in my Android app. That one is automatically full screen on Android.

This is not a Pixel issue, but an Android 15 issue. Seems QML does not properly render emoji on Android 15. Started a new topic for that.

Oh right, thanks for letting me know. At least I know it's not something I've done wrong

@jsulm @mrdebug I probably found appropriate knowledge about approach to programming STM32MP1. The STM32MP1 series is based on Cortex-A7 and Cortex-M4 cores architecture. First Way: First of those (Cortex-A7) is required to create GUI (ex. Boot2Qt) . But second one (Cortex-M4) is required to communicate with STM32 peripheral (ex. by STM32CubeProgrammer). Data processed in Cortex-M4 can be send to GUI (Cortex-M7) over the “Inter processor Communications” (IPC) virtual UART. Second Way: All programing by userspace Linux . In case OpenSTLinux ad STM32MP157f-DK2 , necessery is to turn on CAN0 by editind device tree. Device tree is generated by STM32CubeMX. Just make sure to install the appropriate version of the STM32Cube* tools - supplied with the Ecosystem version you are using.

I thought it is transparent for us. in this section https://developer.android.com/guide/practices/page-sizes?hl=en ... If your app uses any native code, then you should rebuild your app with support for 16 KB devices. If you are unsure if your app uses native code, you can use the APK Analyzer to identify whether any native code is present and then check the alignment of ELF segments for any shared libraries that you find. .. But I don't understand if it is mandary where devices are page size 16KB.

@Aaron-Liao Check this: https://bugreports.qt.io/browse/QTBUG-130576 I have created a bug report for this issue.

Fixed in 6.7.3