Android platform support and APIs
Compilation for Android
The compiler generates an APK file as the output when the
module is imported by the compilation target. The path to the generated
file can be specified using the
Host system configuration
To compile Android apps from a 64 bits GNU/Linux host you can reuse an existing Android Studio installation or make a clean install with command line tools only.
Note that this guide supports only 64 bits GNU/Linux hosts with support for a Java 8 JDK, it may be possible to support other platforms with some tweaks.
Install the required SDK packages using one of these two methods:
a. Using Android Studio, open
Tools > Android > SDK Manager, in the SDK Tools tab, install "Android SDK Build-Tools", CMake and NDK.
b. From the command line, run this script for a quick setup without Android Studio. You will probably need to tweak it to you system or update the download URL to the latest SDK tools from https://developer.android.com/studio/index.html#command-tools
~~~ # Fetch and extract SDK tools mkdir -p ~/Android/Sdk cd ~/Android/Sdk wget https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip unzip sdk-tools-linux-3859397.zip # Update tools tools/bin/sdkmanager --update # Accept the licenses tools/bin/sdkmanager --licenses # Install the basic build tools tools/bin/sdkmanager "build-tools;27.0.0" ndk-bundle ~~~
Set the environment variable ANDROID_HOME to the SDK installation directory, usually
~/Android/Sdk/. Use the following command to setup the variable for bash.
echo "export ANDROID_HOME=~/Android/Sdk/" >> ~/.bashrc
Install Java 8 JDK, on Debian/Ubuntu systems you can use the following command:
sudo apt install openjdk-8-jdk
Configure the Android application
The app.nit framework and this project offers some services to customize the generated Android application.
All app.nit annotations are applied to Android projects:
Custom information can be added to the Android manifest file using the annotations
Example usage to specify an extra permission:
android_manifest """<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>"""
The API version target can be specified with
android_api_target. These take a single integer as argument. They are applied in the Android manifest as
android_activitydefines a Java class used as an entry point to your application. As of now, this annotation should only be used by low-level implementations of Nit on Android. Its usefulness will be extended in the future to customize user applications.
There is two core implementation for Nit apps on Android.
android::nit_activity is used by apps with standard windows and native UI controls.
android::game is used by, well, games and the game frameworks
Clients don't have to select the core implementation, it is imported by other relevant modules.
For example, a module importing
android will trigger the importation of
Lock app orientation
android::portrait locks the generated
application in the specified orientation. This can be useful for games and
other multimedia applications.
Resources and application icon
Resources specific to the Android platform should be placed in an
android/ folder at the root of the project.
The folder should adopt the structure of a normal Android project, e.g., a custom XML resource file can be placed
android/res/values/color.xml to be compiled with the Android application.
The application icon should also be placed in the
Place the classic bitmap version at
android/res/mipmap-hdpi/ic_launcher.png (and others),
and the adaptive version at
The Nit compiler detects these files and uses them as the application icon.
android/ folders may be placed next to more specific Nit modules to change the Android resources
for application variants. The more specific resources will have priority over the project level
There are two compilation modes for the Android platform, debug and release.
Theses modes are also applied to the generated Android projects.
The compilation mode is specified as an argument to
--release can be specified as debug is the default behavior.
Debug mode enables compiling to an APK file without handling signing keys and their password. The APK file can be installed to a local device with USB debugging enabled, but it cannot be published on the Play Store.
nitc will compile Android applications in debug mode.
Building in release mode will use your private key to sign the APK file, it can then be published on the Play Store.
Have a keystore with a valid key to sign your APK file.
To create a new keystore, avoid using the default values of
jarsigneras they change between versions of the Java SDK. You should instead use a command similar to the following, replacing
KEY_ALIASwith the desired values.
keytool -genkey -keystore KEYSTORE_PATH -alias KEY_ALIAS -sigalg MD5withRSA -keyalg RSA -keysize 1024 -validity 10000
Set the environment variables used by
TSA_SERVER. These settings can be set in a startup script such as
~/.bashrcor in a local Makefile.
You can use the following commands by replacing the right-hand values to your own configuration.
export KEYSTORE=keystore_path export KEY_ALIAS=key_alias export TSA_SERVER=timestamp_authority_server_url # Optional
--releaseoptions. You will be prompted for the required passwords as needed by