GitLab

We meanwhile have apps that need it in multiple places, so this actually
hurts more than it helps.

This reduces the difference to a manual local setup and thus the
re-usability of cached packages.

While useful for development, our default configuration here is minimum
size release builds, not the best choice for doing development work anyway.
So, let's rather fully optimize for the end user/release scenario, as this
removes a few plugins from each of our APKs.

We neither use nor can/want to use that. Saves compilation time and
package size.

Some of those are rather asset-heavy and thus impact the APK and
installation size.

Now that we can build both QtSvg and QtQuickControls2 without pulling in
QtWidgets that has no negative impact on apps not using widgets anymore.

Plasma Phonebook and Calindori need that (via QAction in KPeople), but we
don't want to force it on everyone else. There's one more place that needs
sorting out though, the QtQuickControls2 platform module.

Due to how QtSvg depends on QtWidgets we cannot do this in a less invasive
way unfortunately, but with the recent Qrca fixes all current Craft Android
builds work with this, and lose a few MB in their APKs.

The Google Play store unfortunately insist on 64bit packages for every
architecture we add, otherwise you cannot even create a new release there.

Volker Krause authored Apr 05, 2021 and Ben Cooksley committed Apr 23, 2021

This covers ARM 32/64 bit (the primary target platforms) as well as 32bit
x86 (the emulator platform). 64bit x86 works as well should we need that
at some point.

So far only KDE Itinerary is included, as this is aiming at actual
production releases I didn't want to add other apps without explicit
maintainer approval/involvement. In theory adding more apps is just a few
config file entries, realistically I'd also expect a few more Android
specific Craft fixes as well though.

Signing and deploying the packages is still missing, but this should be
good enough to validate the Craft use and the resulting packages at least.

The Jenkins part of this is a blind copy/paste job from the corresponding
Windows setup, the Craft part I have tested locally in the Android docker.

This depends on packaging/craftmaster!2
and the 21.04.0 release to become available.

Keep the normal PKG_CONFIG_PATH intact to allow finding opengl
and x11 dependencies that are not build via craft.

Include the additional information our new certificate contains to allow the code signing checks on Appx bundles to pass