Building Krita for Android

Use Linux to build Krita for Android. Building Krita for Android on another system is NOT supported yet. There are two approaches for building Krita for Android: one with CI’s docker image, and the other one straight in the host system.

Using prebuilt docker image

Docker approach is based on the normal linux-docker builds approach. You might want to check the details in the original document for Linux: Krita Docker Image

Here we expect that you have already performed all the Prerequisites steps and downloaded Krita sources using the original document.

Fetch CI-management repositories

For building on Android we need the toolchain files from the ci-management repository, so fetch them:

pushd ./persistent/krita
git clone https://invent.kde.org/dkazakov/krita-deps-management.git
git clone https://invent.kde.org/dkazakov/ci-utilities.git krita-deps-management/ci-utilities
popd

Building the Android container

Firstly you need to download all Krita dependencies and QtCreator. When fetching the dependencies you need to select he target architecture: x86_64, armeabi-v7a or arm64-v8a.

# download the dependencies and QtCreator
./bin/bootstrap-deps.sh --android=x86_64

# if you don't want to fetch QtCreator, but only deps,
# use bootstrap-krita-deps.sh
# ./bin/bootstrap-krita-deps.sh --android=x86_64

This script will set up the full SDP environment in ./persistent/deps folder. The deps themselves will be located in ./persistent/deps/_install

Now build the docker image and run the container. Just pass the --android flag to the build_image script and it will fetch the correct image for you:

./bin/build_image --android
./bin/run_container

If you are hard on harddrive space, you can cleanup the caches using the cleanup section of the original manual.

Enter the container and build Krita

# enter the container
./bin/enter

You need to manually set up a few environment variables and folders (they might be automated later, but not right now):

# set ABI you are building for
export KDECI_ANDROID_ABI=x86_64

# location where _build and _packaging folders will be located
# (don't change)
export KDECI_WORKDIR_PATH=/home/appimage/appimage-workspace

# location where the dependencies were unpacked (don't change)
export KDECI_SHARED_INSTALL_PATH=/home/appimage/appimage-workspace/deps/usr

Ostrzeżenie

Currently, you need to set up these variable every time you enter the container!

Then create the build directory and enter it (don’t change the location, since it is tightly linked to $KDECI_WORKDIR_PATH in the packaging scripts)

mkdir -p /home/appimage/appimage-workspace/krita/_build
cd /home/appimage/appimage-workspace/krita/_build

Configure Krita:

cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo \
      -DHIDE_SAFE_ASSERTS=OFF \
      -DBUILD_TESTING=OFF \
      -DCMAKE_INSTALL_PREFIX=~/appimage-workspace/deps/usr/ \
      -DCMAKE_TOOLCHAIN_FILE=~/persistent/krita/krita-deps-management/tools/android-toolchain-krita.cmake \
      -DANDROID_ENABLE_STDIO_FORWARDING=ON \
      ~/persistent/krita/

There are two important switches that are unique to Android platform:

1. CMAKE_INSTALL_PREFIX is set to the same folder as the dependencies themselves. It is necessary, because APK packaging scripts cannot search in separate directories.

2. CMAKE_TOOLCHAIN_FILE should point to a special toolchain file that will read custom environment variables (pre-set in the docker containter) and locates SDK and NDK paths.

3. Enable ANDROID_ENABLE_STDIO_FORWARDING to get proper logging in «logcat». This option enables manual forwarding of stdout and stderr into logcat-logger.

Then build Krita as usual:

make -j8 install

Building the APK package

If you set up KDECI_WORKDIR_PATH and KDECI_SHARED_INSTALL_PATH properly, then just do:

python ~/persistent/krita/build-tools/ci-scripts/build-android-package.py

And you will get an APK package in $KDECI_WORKDIR_PATH/krita/_packaging

If you happen to need an AAB package, then you need to generate a bit more artifacts:

python ~/persistent/krita/build-tools/ci-scripts/build-android-package.py --archive-artifacts
python ~/persistent/krita/build-tools/ci-scripts/build-android-appbundle.py

The first command will build and APK and package all artifacts in $KDECI_WORKDIR_PATH/krita/_packaging/krita_build_apk and the second script will reuse these artifacts for building AAB package.

Troubleshooting

The ground truth for the docker builds is the android.yml script that is used on CI. If you have a suspicion that this manual got outdated, please compare it to the original android.yml file

Using your host system for Android development

If you chose to build on your host system, you will have much more troubles to resolve, because you need to set up all SDK and NDK things.

First configure prefix variable where we install our SDKs:

export ANDROID_ROOT=/home/appimage/appimage-workspace/android/

Right now we use Android NDK version r22b to do our builds. So, it is recommended to use that. Download it from google’s website then extract it into $ANDROID_ROOT

Next you need to download command line tools that will let you install the SDKs and build tools. Look for links to commandlinetools at the bottom of android studio page. Download and extract the tools into $ANDROID_ROOT.

Podpowiedź

Theoretocally, you can try installing the whole Android Studio and configure everything within the Studio itself, but this way is not supported currently (noone just tried that).

If you go with the Android Studio approach then open SDK manager and download Android SDK Build-Tools (more info in the official documentation)

Configure environment variables

export KDECI_ANDROID_SDK_ROOT=$ANDROID_ROOT/sdk
export KDECI_ANDROID_NDK_ROOT=$ANDROID_ROOT/android-ndk-r22b/
export ANDROID_HOME=$ANDROID_ROOT/sdk
export PATH="$ANDROID_ROOT/sdk/platform-tools/:$ANDROID_ROOT/cmdline-tools/bin/:$PATH"

Informacja

You might want to put these variables into some env file and source it before every use of Android environment

Installing Prerequisites

To build Krita for Android you need to have a specific version of Java installed on your machine:

sudo add-apt-repository ppa:openjdk-r/ppa
sudo apt-get update
sudo apt-get install openjdk-17-jdk # exactly this version!

Check if no other version of Java is installed. If installed, either remove it (recommended) or make sure Ubuntu’s update-alternatives pulls exactly version 17 for javac and the runtime (no idea how to check that).

# make sure both commands link to version 17!
javac --version
ls -l /usr/lib/jvm/*

Make sure that you have Python of version 3.10 installed:

> python --version
Python 3.10.13

Informacja

Theoretically, Python 3.9 may also work, but it is not tested. Python 3.8 will not work, that is tested.

Install SDKs and build tools:

yes | sdkmanager --sdk_root=$KDECI_ANDROID_SDK_ROOT --licenses
sdkmanager --sdk_root=$KDECI_ANDROID_SDK_ROOT platform-tools
sdkmanager --sdk_root=$KDECI_ANDROID_SDK_ROOT "platforms;android-33"
sdkmanager --sdk_root=$KDECI_ANDROID_SDK_ROOT "build-tools;30.0.3"
sdkmanager --sdk_root=$KDECI_ANDROID_SDK_ROOT "build-tools;34.0.0"
sdkmanager --sdk_root=$KDECI_ANDROID_SDK_ROOT emulator
sdkmanager --sdk_root=$KDECI_ANDROID_SDK_ROOT tools

Podpowiedź

Krita’s current minimal API-level is android-23. We can theoretically install the latest avalable SDK and NDK that still supports this API-level. Though we update not that often, so our versions may drag a little behind.

The backwards compatibility of NDK and SDK can be checked here:

• NDK: https://developer.android.com/ndk/downloads/revision_history

• SDK: where???

Fetch Krita Deps

Choose sources and environment directories:

export SRCDIR=/home/appimage/persistent/sources
export ENVDIR=/home/appimage/persistent/envdir

mkdir -p $SRCDIR
mkdir -p $ENVDIR

$SRCDIR will store all sources and build artifacts, but $ENVDIR will store packages and caches.

Checkout Krita repository and all the management repositories:

cd $SRCDIR

git clone https://invent.kde.org/graphics/krita.git
git clone https://invent.kde.org/dkazakov/krita-deps-management.git krita/krita-deps-management
git clone https://invent.kde.org/dkazakov/ci-utilities.git krita/krita-deps-management/ci-utilities

Install python dependencies. You might want to use Python’s venv feature for this:

# set up venv
python3.10 -m venv --upgrade-deps $WORKDIR/PythonEnv
source $WORKDIR/PythonEnv/bin/activate

# install requirements
python -m pip install -r $SRCDIR/krita/krita-deps-management/requirements.txt

Set up an environment variable for the target android architecture:

export KDECI_ANDROID_ABI=x86_64

Set up working directory and environment:

cd $SRCDIR/krita
python krita-deps-management/tools/setup-env.py \
    # Path to our venv to make sure it is automatically activated in this environment
    -v $WORKDIR/PythonEnv \
    # select target ABI
    --android-abi $KDECI_ANDROID_ABI \
    # select workdir root (where the caches and downloads will go)
    --root $WORKDIR

# activate the generated environment
source $WORKDIR/base-env

# generate deps file
python krita-deps-management/tools/generate-deps-file.py \
    -s krita-deps-management/latest/krita-deps.yml \
    -o .kde-ci.yml

# fetch the dependencies
python krita-deps-management/ci-utilities/run-ci-build.py \
    # requitred fields for the script
    --project krita --branch master \
    # platform for which to fetch dependencies
    --platform Android/$KDECI_ANDROID_ABI \
    # only generate environment file in `./env`
    --only-env

# activate generated environment

source ./env

Informacja

Next time you enter the environment, you just neet to perform the latest environment set up using source ./env. It will activate all your manual configurations as well, like Python’s venv, KDECI_ANDROID_SDK_ROOT and KDECI_ANDROID_ABI.

Configure Krita:

cd $SRCDIR/krita/_build
cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo \
    -DHIDE_SAFE_ASSERTS=OFF \
    -DBUILD_TESTING=OFF \
    -DCMAKE_INSTALL_PREFIX=$SRCDIR/krita/_install \
    -DCMAKE_TOOLCHAIN_FILE=$SRCDIR/krita/krita-deps-management/tools/android-toolchain-krita.cmake \
    -DANDROID_ENABLE_STDIO_FORWARDING=ON \
    $SRCDIR/krita/

There are two important switches that are unique to Android platform:

1. CMAKE_INSTALL_PREFIX is set to the same folder as the dependencies themselves. It is necessary, because APK packaging scripts cannot search in separate directories.

2. CMAKE_TOOLCHAIN_FILE should point to a special toolchain file that will read custom environment variables (pre-set in the docker containter) and locates SDK and NDK paths.

3. Enable ANDROID_ENABLE_STDIO_FORWARDING to get proper logging in «logcat». This option enables manual forwarding of stdout and stderr into logcat-logger.

Then build Krita as usual:

make -j8 install

Building the APK package

When building outside docker it is important that _install and _build folders are placed straight in the Krita source tree. That allows APK building scripts to find the assets properly, since it searches stuff relative to the current working directory:

cd $SRCDIR/krita
python build-tools/ci-scripts/build-android-package.py

And you will get an APK package in _packaging subfolder.

If you happen to need an AAB package, then you need to generate a bit more artifacts:

cd $SRCDIR/krita
python build-tools/ci-scripts/build-android-package.py --archive-artifacts
python build-tools/ci-scripts/build-android-appbundle.py

The first command will build and APK and package all artifacts in _packaging/krita_build_apk and the second script will reuse these artifacts for building AAB package.

Troubleshooting

The ground truth for building the environment (i.e. setting up SDK, NDK and Python) is the Dockerfile used on CI

The ground truth for the actual build of Krita is android.yml script that is used on CI. If you have a suspicion that this manual got outdated, please compare it to the original android.yml file

Installing Android Emulator

Using Android emulator is easy, after it is configured initially. The only issue that worth remembering is that when using x86_64 builds the host system should support KVM virtualization. KVM virtualization is not required for emulating ARM target.

Ostrzeżenie

[TODO] Krita docker does not automatically add «kvm» group into the client system (yet), it should be done manually:

1. Add kvm group into the docker with the same group-id as on the host machine

2. Add appimage user into kvm group

3. Relogin into the appimage user for the changes to take effect

Install cpu-checker and check if KVM is supported on your system (or in the docker container):

sudo apt-get install cpu-checker
# Check if kvm is available
kvm-ok

Install the system image for the target system. Change x86_64 to the target architecture you would like to test:

sdkmanager --sdk_root=$KDECI_ANDROID_SDK_ROOT "system-images;android-23;google_apis;x86_64"

Create the virtual device:

# save the device name
export device_name=Test_API_23

# create the device
avdmanager create avd --force --name $device_name --abi x86_64 --package 'system-images;android-23;google_apis;x86_64'

# create an SD card for the device
mksdcard -l testsdcard 512M ~/sdcard.img

Open configuration file for the new device (located at ~/.android/avd/Test_API_23.avd/config.ini) and edit the following values:

# increase cache size
disk.cachePartition.size=512MB

# increase the size of the root partition
disk.dataPartition.size=3000M

# if using x86_64 or arm64-v8a targets, enable GPU acceleration
hw.gpu.enabled=yes
hw.gpu.mode=auto

# make sure that the screen size is not too tiny
hw.lcd.density=180
hw.lcd.depth=16
hw.lcd.height=1080
hw.lcd.vsync=60
hw.lcd.width=1920

# increase the amount of RAM available for the device
hw.ramSize=4096M

# set up teh SD card
sdcard.size=512 MB
sdcard.path=<path to your sd card>/sdcard.img

# increase the size of VM heap
vm.heapSize=1024M

Run the emulator (add -wipe-data switch if you would like to reset the device):

emulator -avd $device_name -no-snapshot -no-boot-anim

Install Krita on the device:

adb install ./krita-x86_64-5.2.0-prealpha-debug.apk

When the container it not needed anymore, it can be removed with the follwoing command:

avdmanager delete avd -n $device_name

When you change something in the Krita’s code, you should rebuild the pacakge and reinstall it onto your device (or emulator).

Firstly, you need to manually set up environment variables, that are usually set up by build-android-package.py:

export ANDROID_ABI=$KDECI_ANDROID_ABI
export KRITA_INSTALL_PREFIX=$KDECI_SHARED_INSTALL_PATH

Then just run the build and deploy steps in one line:

cd cd $SRCDIR/krita/_build/krita_build_apk
make -j8 install -C .. && ./gradlew installDebug && adb shell am start -n "org.krita.debug/org.krita.android.MainActivity"

This command will do four things:

1. Rebuild Krita itself

2. Build a debugging version of a package using existing apk artifacts directories

3. Install the package on the currently connected device (or emulator)

4. Run Krita on the currently connected device (or emulator)

If Krita crashes you can look up the logs using adb logcat