deprecated in favor of https://github.com/rust-windowing/android-ndk-rs which works with winit master
Android Glue
Usage
With Docker
The easiest way to compile for Android is to use Docker and the philipalldredge/cargo-apk image.
In order to build an APK, simply do this:
docker run --rm -v <path-to-local-directory-with-Cargo.toml>:/root/src philipalldredge/cargo-apk cargo apk build
For example if you're on Linux and you want to compile the project in the current working directory.
docker run --rm -v "$(pwd):/root/src" -w /root/src philipalldredge/cargo-apk cargo apk build
Do not mount a volume on /root or you will erase the local installation of Cargo.
After the build is finished, you should get an Android package in target/android-artifacts/debug/apk.
Manual usage
Setting up your environment
Before you can compile for Android, you need to setup your environment. This needs to be done only once per system.
- Install
rustup. - Run
rustup target add <target>for all supported targets to which you want to compile. Building will attempt to build for all supported targets unless the build targets are adjusted viaCargo.toml.rustup target add armv7-linux-androideabirustup target add aarch64-linux-androidrustup target add i686-linux-androidrustup target add x86_64-linux-android
- Install the Java JRE or JDK (on Ubuntu,
sudo apt-get install openjdk-8-jdk). - Download and unzip the Android NDK.
- Download and unzip the Android SDK.
- Install some components in the SDK:
./android-sdk/tools/bin/sdkmanager "platform-tools" "platforms;android-29" "build-tools;29.0.0". - Install
cargo-apkwithcargo install cargo-apk. - Set the environment variables
NDK_HOMEto the path of the NDK andANDROID_HOMEto the path of the SDK.
Compiling
In the project root for your Android crate, run cargo apk build. You can use the same options as with the regular cargo build.
This will build an Android package in target/android-artifacts/<debug|release>/apk.
Compiling Multiple Binaries
cargo apk build supports building multiple binaries and examples using the same arguments as cargo build. It will produce an APK for each binary.
Android packages for bin targets are placed in target/android-artifacts/<debug|release>/apk.
Android packages for example targets are placed in target/android-artifacts/<debug|release>/apk/examples.
Testing on an Android emulator
Start the emulator, then run:
cargo apk run
This will install your application on the emulator, then run it.
If you only want to install, use cargo apk install.
To show log run: cargo apk logcat | grep RustAndroidGlueStdouterr
Interfacing with Android
An application is not very useful if it doesn't have access to the screen, the user inputs, etc.
The android_glue crate provides FFI with the Android environment for things that are not in the stdlib.
How it works
The build process
The build process works by:
- Using rustc to always compile your crate as a shared library by:
- Creating a custom CMake toolchain file and setting environment variables which expose the appropriate NDK provided build tools for use with the
ccandcmakecrates. - Creating a temporary file in the same directory as your crate root. This temporary file serves as the crate root of the static library. It contains the contents of the original crate root along with an
android_mainimplementation. - Compiling a forked version of
android_native_app_glue.android_native_app_glueis originally provided by the NDK. It provides the entrypoint used by Android'sNativeActivitythat callsandroid_main. - Linking using the NDK provided linker.
- Creating a custom CMake toolchain file and setting environment variables which expose the appropriate NDK provided build tools for use with the
This first step outputs a shared library, and is run once per target architecture.
The command then builds the APK using the shared libraries, generated manifest, and tools from the Android SDK. If the C++ standard library is used, it adds the appropriate shared library to the APK. It signs the APK with the default debug keystore used by Android development tools. If the keystore doesn't exist, it creates it using the keytool from the JRE or JDK.
Supported [package.metadata.android] entries
# The target Android API level.
# "android_version" is the compile SDK version. It defaults to 29.
# (target_sdk_version defaults to the value of "android_version")
# (min_sdk_version defaults to 18) It defaults to 18 because this is the minimum supported by rustc.
android_version = 29
target_sdk_version = 29
min_sdk_version = 26
# Specifies the array of targets to build for.
# Defaults to "armv7-linux-androideabi", "aarch64-linux-android", "i686-linux-android".
build_targets = [ "armv7-linux-androideabi", "aarch64-linux-android", "i686-linux-android", "x86_64-linux-android" ]
# The following values can be customized on a per bin/example basis. See multiple_targets example
# If a value is not specified for a secondary target, it will inherit the value defined in the `package.metadata.android`
# section unless otherwise noted.
#
# The Java package name for your application.
# Hyphens are converted to underscores.
# Defaults to rust.<target_name> for binaries.
# Defaults to rust.<package_name>.example.<target_name> for examples.
# For example: for a binary "my_app", the default package name will be "rust.my_app"
# Secondary targets will not inherit the value defined in the root android configuration.
package_name = "rust.cargo.apk.advanced"
# The user-friendly name for your app, as displayed in the applications menu.
# Defaults to the target name
# Secondary targets will not inherit the value defined in the root android configuration.
label = "My Android App"
# Internal version number used to determine whether one version is more recent than another. Must be an integer.
# Defaults to 1
# See https://developer.android.com/guide/topics/manifest/manifest-element
version_code = 2
# The version number shown to users.
# Defaults to the cargo package version number
# See https://developer.android.com/guide/topics/manifest/manifest-element
version_name = "2.0"
# Path to your application's resources folder.
# If not specified, resources will not be included in the APK
res = "path/to/res_folder"
# Virtual path your application's icon for any mipmap level.
# If not specified, an icon will not be included in the APK.
icon = "@mipmap/ic_launcher"
# Path to the folder containing your application's assets.
# If not specified, assets will not be included in the APK
assets = "path/to/assets_folder"
# If set to true, makes the app run in full-screen, by adding the following line
# as an XML attribute to the manifest's <application> tag :
# android:theme="@android:style/Theme.DeviceDefault.NoActionBar.Fullscreen
# Defaults to false.
fullscreen = false
# The maximum supported OpenGL ES version , as claimed by the manifest.
# Defaults to 2.0.
# See https://developer.android.com/guide/topics/graphics/opengl.html#manifest
opengles_version_major = 3
opengles_version_minor = 2
# Adds extra arbitrary XML attributes to the <application> tag in the manifest.
# See https://developer.android.com/guide/topics/manifest/application-element.html
[package.metadata.android.application_attributes]
"android:debuggable" = "true"
"android:hardwareAccelerated" = "true"
# Adds extra arbitrary XML attributes to the <activity> tag in the manifest.
# See https://developer.android.com/guide/topics/manifest/activity-element.html
[package.metadata.android.activity_attributes]
"android:screenOrientation" = "unspecified"
"android:uiOptions" = "none"
# Adds a uses-feature element to the manifest
# Supported keys: name, required, version
# The glEsVersion attribute is not supported using this section.
# It can be specified using the opengles_version_major and opengles_version_minor values
# See https://developer.android.com/guide/topics/manifest/uses-feature-element
[[package.metadata.android.feature]]
name = "android.hardware.camera"
[[package.metadata.android.feature]]
name = "android.hardware.vulkan.level"
version = "1"
required = false
# Adds a uses-permission element to the manifest.
# Note that android_version 23 and higher, Android requires the application to request permissions at runtime.
# There is currently no way to do this using a pure NDK based application.
# See https://developer.android.com/guide/topics/manifest/uses-permission-element
[[package.metadata.android.permission]]
name = "android.permission.WRITE_EXTERNAL_STORAGE"
max_sdk_version = 18
[[package.metadata.android.permission]]
name = "android.permission.CAMERA"
Environment Variables
Cargo-apk sets environment variables which are used to expose the appropriate C and C++ build tools to build scripts. The primary intent is to support building crates which have build scripts which use the cc and cmake crates.
- CC : path to NDK provided
clangwrapper for the appropriate target and android platform. - CXX : path to NDK provided
clang++wrapper for the appropriate target and android platform. - AR : path to NDK provided
ar - CXXSTDLIB :
c++to use the full featured C++ standard library provided by the NDK. - CMAKE_TOOLCHAIN_FILE : the path to the generated CMake toolchain. This toolchain sets the ABI, overrides any target specified, and includes the toolchain provided by the NDK.
- CMAKE_GENERATOR :
Unix Makefilesto default toUnix Makefilesas opposed to using the CMake default which may not be appropriate depending on platform. - CMAKE_MAKE_PROGRAM: Path to NDK provided make.
C++ Standard Library Compatibility Issues
When a crate links to the C++ standard library, the shared library version provided by the NDK is used. Unfortunately, dependency loading issues will cause the application to crash on older versions of android. Once lld linker issues are resolved on all platforms, cargo apk will be updated to link to the static C++ library. This should resolve the compatibility issues.
6 Dec 31, 2022
193 Dec 5, 2022
13 Dec 13, 2022
3 Feb 28, 2024
1 Dec 17, 2021
7 Dec 25, 2022
28 Dec 21, 2022
14 Nov 23, 2022
6 Mar 31, 2023
39 May 10, 2021
44 Aug 13, 2022
90 Jan 3, 2023
4 May 2, 2022
6 Oct 21, 2023
173 Dec 17, 2022
11 Mar 10, 2024
1.2k Dec 29, 2022
3 Oct 18, 2021
7k Jan 7, 2023