Android/Environment via Container: Difference between revisions
< Android
No edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
This image alone contains a working Android SDK, NDK and Qt binaries. The easiest is to access it like this (it will be downloaded the first time you use it): | This image alone contains a working Android SDK, NDK and Qt binaries. The easiest is to access it like this (it will be downloaded the first time you use it): | ||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
docker run -ti --rm kdeorg/android-sdk bash | docker run -ti --rm kdeorg/android-arm-sdk bash | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| Line 14: | Line 14: | ||
To make it easy to compile applications we put some scripts to get started. They can be triggered like this: | To make it easy to compile applications we put some scripts to get started. They can be triggered like this: | ||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
docker run -ti --rm kdeorg/android-sdk /opt/helpers/build-generic <appname> | docker run -ti --rm kdeorg/android-arm-sdk /opt/helpers/build-generic <appname> | ||
</syntaxhighlight> | </syntaxhighlight> | ||
The following command will compile okular with all its dependencies and output an apk to our | The following command will compile okular with all its dependencies and output an apk to our /tmp directory. | ||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
docker run -ti --rm -v /tmp:/output kdeorg/android-sdk /opt/helpers/build-generic okular | docker run -ti --rm -v /tmp:/output kdeorg/android-arm-sdk /opt/helpers/build-generic okular | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| Line 25: | Line 25: | ||
* build-generic fetch the dependencies of <appname>, build them and then build <appname>, outputting an apk to /output. Therefore a volume to /output will catch the result. e.g. <code>-v $HOME/apks:/output</code> | * build-generic fetch the dependencies of <appname>, build them and then build <appname>, outputting an apk to /output. Therefore a volume to /output will catch the result. e.g. <code>-v $HOME/apks:/output</code> | ||
* if we want to develop locally a project, we can also use volumes and put them in the home directory. e.g. <code>-v /home/apol/devel/frameworks/kate:/home/user/src/kate</code>. | * if we want to develop locally a project, we can also use volumes and put them in the home directory. e.g. <code>-v /home/apol/devel/frameworks/kate:/home/user/src/kate</code>. | ||
* Note we are passing kdeorg/android-arm-sdk, this is to produce 32-bit arm images, there's also kdeorg/android-aarch64-sdk available as well. | |||
Revision as of 23:08, 5 August 2019
Using Docker for KDE on Android Development
This is the easiest way to start cross-compiling and developing Qt applications for Android. The explained Docker image will install all dependencies and setup all environment variables automatically. By this, it closely follows the steps explained in the detailed system setup guide:
Setting up
This image alone contains a working Android SDK, NDK and Qt binaries. The easiest is to access it like this (it will be downloaded the first time you use it):
docker run -ti --rm kdeorg/android-arm-sdk bash
Here one can start developing at ease in an environment welcoming to projects that use cmake, Qt, ECM, etc.
Building an application
To make it easy to compile applications we put some scripts to get started. They can be triggered like this:
docker run -ti --rm kdeorg/android-arm-sdk /opt/helpers/build-generic <appname>
The following command will compile okular with all its dependencies and output an apk to our /tmp directory.
docker run -ti --rm -v /tmp:/output kdeorg/android-arm-sdk /opt/helpers/build-generic okular
Tricks
- build-generic fetch the dependencies of <appname>, build them and then build <appname>, outputting an apk to /output. Therefore a volume to /output will catch the result. e.g.
-v $HOME/apks:/output - if we want to develop locally a project, we can also use volumes and put them in the home directory. e.g.
-v /home/apol/devel/frameworks/kate:/home/user/src/kate. - Note we are passing kdeorg/android-arm-sdk, this is to produce 32-bit arm images, there's also kdeorg/android-aarch64-sdk available as well.