Mobile and Embedded

@Vineela as far as I know, yes. if you set the font somewhere from your quellcode, via StyleSheet or object->setFont(), then the default font won't have any effect on that object.

Hi, I described the steps I followed in a post over here, https://mechatronicsblog.com/cross-compile-and-deploy-qt-5-12-for-raspberry-pi/ Some people found some issues and posted comments there, the “qendian” issue seems to be related to this bug, there is also a patch there. https://bugreports.qt.io/browse/QTBUG-71945

Hi Hilk, I have seen that link earlier but did not go through in details. Seems that comments for that also very useful. Thanks.

@J.Hilk Thank you :)

Very late in reply but if you still are interested there is also this library called QtAndroidTools containing various tool for access android features from QML. Currently it still in progress but it contain the tool for add abmob ad in a very easy way. Check the example provided in the project. https://github.com/FalsinSoft/QtAndroidTools

@J.Hilk Oh, that's silly :-( Thanks for your advice!

@comet91-0 Again, first match when searching for "Qt Android" in Google: http://doc.qt.io/qt-5/android.html

@aha_1980 Thanks for your inputs @aha_1980 .

Answering my own question, meta-qt5 is licensed under the MIT License. So I can use it without restriction. P.S.: I thought I couldn't use meta-qt5 without holding a Qt Commercial License because I saw there is a Qt-Company-Commercial license file in the directory licenses. But those are (I guess) licenses for Qt Software, not meta-qt5 layer.

Done. Thanks for all the help.

@comet91-0 if your issue is solved please don't forget to mark your post as such! Thanks.

@comet91-0 you need to either install the precompiled Qt-libs for android (from the online installer) or compile it yourself.

I ran the bitbake process a second time, and now it succeeded. I guess that some interruptions of the first build process somehow led to inconsistent build caches. For example git-lfs was missing (but this was detected right at the beginning of the build process, so I don‘t think this was the culprit). So I went through the b2qt build instructions once again. But this time I updated the required software packages using $> sudo apt-get install gawk curl git-core diffstat unzip p7zip-full texinfo gcc-multilib build-essential chrpath libsdl1.2-dev xterm gperf bison g++-multilib This resulted in some software packages being added and some existing being upgraded I ran bitbake from a virtual console I am running xubuntu 16.04 LTS and recently my desktop sessions sometime have been closed, when bitbake ran for a while. So I decided not to run bitbake from a GUI terminal, but from a virtual text console. I created a new build environment from scratch I created a new directory for the b2qt build environment and ran the b2qt-init-build-env script from there. So I was sure there was no old stuff laying around. As already said, „$> bitbake b2qt-embedded-qt5-image“ then successfully built the image. Problem solved.

@J-Hilk Yes, I can start two instances of creator and use different settings for Android devices. Not really comfortable, but it is working.

@Amin-Ji sudo apt-get install qtcreator after installation you may(or may not ) need to make a 5.12 kit. Changes are it's automatically detected as well

@dogbear said in Android deployment... how to deploy images for app to load: It's better if I can just load the images from disk at runtime. and much slower. Anyway you can add the images to the assets folder and access them (even out of QML iirc) with an asset:// url https://community.kde.org/Necessitas/Assets The assets folder can be found in the path you specified via ANDROID_PACKAGE_SOURCE_DIR qmake variable

@raven-worx OK, thanks. That seems to work.

@morte said in detecting status ("on"/"off") of location services: This is brobably Qt bug I'd call it working as designed, although the design could differ from your expectations :-) Seriuosly, I guess you can post a feature request to ask for the error status to be cleared once positioning data resumes. For the time being, I guess you need to stop checking for error status once you resume receiving data, or you could even emit a signal of your own once you know data is back again.