Qt for Device Creation is already pre-configured and has pre-built images for several target devices. Not to mention it uses the commercial license so you don't have to release the source code. It also comes with support if you need it. But for a hobby project, I think the open-source version is okay if you're prepared to set up everything by yourself.
Oh! Almost forgot. Qt Extended/Qtopia (a subset of Qt Embedded- I think this was also GPL at one point) was once released under the GPL license but it was discontinued back in 2009 when Nokia owned Qt. It was designed for embedded Linux-based mobile devices like the Greenphone or the Neo FreeRunner. After the discontinuation, it was forked in QtMoko but I don't think it's being developed anymore.
Execute this command to install Qt in the /usr/local/Qt-4.8.5-arm/ directory : ./configure -opensource -confirm-license -prefix /usr/local/Qt-4.8.5-arm -embedded arm -little-endian -no-pch -xplatform qws/linux-arm-gnueabi-g++
In this step Did you create /usr/local/Qt-4.8.5-arm/ directory ? or Did created by qt creator when installitaion?
Yes, i have QT += multimedia in my .pro file. I am trying to run programs from QT examples, but I haven't QML multimedia plugins inside my Linux embedded system. In /usr/lib/qml there is no QtMultimedia directory with multimedia plugins needed to use QML multimedia elements like Camera or MediaPlayer
root# opkg files qtmultimedia-qmlplugins
Package qtmultimedia-qmlplugins (5.12.3+git0+64981aee3b-r0) is installed on root and has the following files:
@SimonHill No, you don't. But if some user of your app asks you to provide object files (*.o, *.obj) you have to, because LGPLv3 requires you to allow users to relink your app against their own Qt version.
I have simular problem. I try to use same as you say:
NDK 19c 64bit
QT creator 4.9.2
For me program strart, but in the debuging mode, breakpoint dont stop if i try to use on Android 4.4.4. If i try to start debuging on Android 9 everythings work okey. I have to use old Android version becouse we use on our system. After i start on old Android version i get message like this:
08:11:14: The command "E:\Android\sdk\platform-tools\adb.exe" terminated with exit code 1.
08:11:14: Package deploy: Failed to pull "/system/bin/app_process32" to "Android_for_armeabi_v7a_Clang_Qt_5_12_4_for_Android_ARMv7-Debug/app_process".
I think the main problem that qt try to use app_process32 and he cant find it becouse on old Android version there is only app_process .
So how to change app_process32 to app_process on qt debuging mode? I try to search in google but i didnt find correct answer.
I found that i can change in ndk-gdb.py file but i change anything it have no changes....i try to delete file and load program, and it was started...so i dont understand from where are taking to load app_process32 but not app_process
@closx The difference between QtWidgets and QML is that QML uses OpenGL for acceleration and QtWidgets doesn't. It looks like your system currently does not really suport OpenGL. Try to install Mesa packages.
Yes. The problem seems to come from the fact that Android versions < 6.0 do not have the TLS 1.2 protocol enabled.
So, the most prudent thing to do is to stay at the version of Qt 5.12.3 to maintain compatibility with the Android versions < 6.0
Hello Google Play Developer,
By August 1, 2019, all apps that use native code must provide a 64-bit version in order to publish an update. As of the sending of this email, at least one of your apps* does not yet meet the requirement: