A meta-project which contains all tasks and repositories related to packaging and releasing KDE software on Android.
Apr 25 2019
Mar 4 2019
Feb 7 2019
Jan 25 2019
Jan 9 2019
Dec 27 2018
Dec 22 2018
- Delete everything in android-builder and point to kdeorg/android-sdk
@dfaure it's absolutely fine for me to dump this repository and reference kdeorg/android-sdk. The ci-tooling repository looks much more mature and we should not have two competing solutions for an infrastructure task (especially, since the ci-tooling one is actively used and maintained)
Dec 21 2018
factorize into build scripts, add qtquickcontrols, select the right version of the tools.
Up to r17c, but now I'll try the CI's dockerfile...
I tried NDK r18 with cmake 3.10, and cmake is missing commit ca97d4cb5 (from cmake git) which adds support for r18 (starting from 3.12.2). Without that fix, cmake can't find the STL, iirc.
yes, cmake cmake-3.10.2 should be ok with any NDK (including NDKr18)
Hi Bogdan, thanks for the info.
I recommend you another approach:
Use sdkmanager (from Android SDK) to install Google's cmake. Personally I'm using it also to install the ndk, but NDKr18 removed the gcc support.
If you need also gcc the best NDK is r17c (has a non-buggy clang and gcc).
Adding Aleix, as I know he's worked on some Android stuff (I only vaguely recall this repository though).
Dec 20 2018
Upgrade to 15c to get a later version of clang 5.0
Dec 7 2018
Nov 16 2018
Nov 14 2018
I wanted to say that http://code.qt.io/cgit/qt/qtandroidextras.git/tree/examples/androidextras/notification is a good start but I changed my mind very fast.
I don't think it's possible to do it entirely from C++, mostly because you need to get notified when the user taps on that notification (I don't know KNotifications API, but I assume it has something like that) , so a small java code is still needed.
I'm offering help on this. I'm quite familiar with the notification Java API, but not so much with Qt on Android.
@mart that piece of code is not that ugly ... it does its job ;-)
From vague memory, I think it should be possible to remove both the widget and the dbus dependency on Android. I'd also focus on the notification frontend API and ignore all the config possibilities on Android.
and we will also eventually need api for having the system bars going over our window as well i guess (like in a photo viewer often you see the photo under the top panel)
in kirigami gallery i'm using this ugly jni code in main.cpp:
Jun 5 2018
Can improve the metadata but some of it is there and that can be improved
May 30 2018
May 19 2018
May 17 2018
I guess this can be closed now, correct?