The Android NDK provides a set of native headers and shared library files that has gradually increased with successive releases of new Android API levels. This page explains these headers and files, and maps them to specific Android API levels.
There are two basic steps to enable your app to use the libraries that the NDK provides:
LOCAL_LDLIBS := -lfoo
To list multiple libraries, use a space as a delimiter. For more information about using the {@code LOCAL_LDLIBS} variable, see Android.mk.
For all API levels, the build system automatically links the standard C libraries, the standard C++ libraries, real-time extensions, and {@code pthread}; you do not need to include them when defining your {@code LOCAL_LDLIBS} variable. For more information about the C and C++ libraries, see Android API level 3.
The NDK often provides new headers and libraries for new Android releases. These files reside under {@code $NDK/platforms/android-<level>/<abi>/usr/include}. When the NDK does not have a specific new group of headers and libraries for an Android API level, it means that an app targeting that level should use the most recently released NDK assets. For example, there was no new release of NDK headers or libraries for Android API levels 6 and 7. Therefore, when developing an app targeting Android API level 7, you should use the headers and libraries located under {@code android-5/}.
Table 1 shows the correspondence between NDK-supported API levels and Android releases.
Table 1. NDK-supported API levels and corresponding Android releases.
| NDK-supported API level | Android release |
|---|---|
| 3 | 1.5 |
| 4 | 1.6 |
| 5 | 2.0 |
| 8 | 2.2 |
| 9 | 2.3 through 3.0.x |
| 12 | 3.1.x |
| 13 | 3.2 |
| 14 | 4.0 through 4.0.2 |
| 15 | 4.0.3 and 4.0.4 |
| 16 | 4.1 and 4.1.1 |
| 17 | 4.2 and 4.2.2 |
| 18 | 4.3 |
| 19 | 4.4 |
| 21 | 4.4W and 5.0 |
Each new release of NDK headers and libraries for a given Android API level is cumulative; you are nearly always safe if you use the most recently released headers when building your app. For example, you can use the NDK headers for Android API level 21 for an app targeting API level 16. By doing so, however, you increase your APK's footprint.
For more information about Android API levels, see What is API Level?.
The NDK provides the following APIs for developing native code that runs on Android 1.5 system images and above.
The C library headers for Android 1.5 are available through their standard names, such as {@code stdlib.h} and {@code stdio.h}. If a header is missing at build time, it's because the header is not available on the 1.5 system image.
An extremely minimal C++ support API is available. For more information on C++ library support, see C++ Library Support.
{@code <android/log.h>} contains various definitions that an app can use to send log messages to the kernel from native code. For more information about these definitions, see the comments in {@code $NDK/platforms/android-3/arch-arm/usr/include/android/log.h}, where {@code $NDK} is the root of your NDK installation.
You can write your own wrapper macros to access this functionality. If you wish to perform logging, your native module should link to {@code /system/lib/liblog.so}. Implement this linking by including the following line in your {@code Android.mk} file:
LOCAL_LDLIBS := -llog
You can use the Zlib compression library by including {@code zlib.h} and {@code zconf.h}. You must also link your native module against {@code /system/lib/libz.so} by including the following line in your {@code Android.mk} file:
LOCAL_LDLIBS := -lz
You can access the Android dynamic linker's {@code dlopen()}, {@code dlsym()}, and {@code dlclose()} functions by including {@code dlfcn.h}. You must also link against {@code /system/lib/libdl.so} by including the following line in your {@code Android.mk} file:
LOCAL_LDLIBS := -ldl
The NDK provides the following APIs for developing native code that runs on Android 1.6 system images and above.
The standard OpenGL ES headers {@code gl.h} and {@code glext.h} contain the declarations necessary for performing OpenGL ES 1.x rendering calls from native code.
To use these headers, link your native module to {@code /system/lib/libGLESv1_CM.so} by including the following line in your {@code Android.mk} file:
LOCAL_LDLIBS := -lGLESv1_CM
All Android-based devices support OpenGL ES 1.0, because Android provides an Open GL 1.0-capable software renderer that can be used on devices without GPUs.
Only Android devices that have the necessary GPU fully support OpenGL ES 1.1. An app can query the OpenGL ES version string and extension string to determine whether the current device supports the features it needs. For information on how to perform this query, see the description of {@code glGetString()} in the OpenGL specification.
Additionally, you must put a {@code <uses-feature>} tag in your manifest file to indicate the version of OpenGL ES that your application requires.
The EGL APIs are only available starting from API level 9. You can, however, use the VM to perform some of the operations that you would get from those APIS. These operations include surface creation and flipping. For an example of how to use {@code GLSurfaceView}, see Introducing GLSurfaceView.
The san-angeles sample application provides an example of how to perform these operations, rendering each frame in native code. This sample is a small Android port of the excellent San Angeles Observation demo program.
The NDK provides the following APIs for developing native code that runs on Android 2.0 system images and above.
The standard OpenGL ES 2.0 headers {@code <GLES2/gl2.h>} and {@code <GLES2/gl2ext.h>} contain the declarations needed for performing OpenGL ES 2.0 rendering calls from native code. These rendering calls provide the ability to use the GLSL language to define and use vertex and fragment shaders.
To use OpenGL ES 2.0, link your native module to {@code /system/lib/libGLESv2.so} by including the following line in your {@code Android.mk} file:
LOCAL_LDLIBS := -lGLESv2
Not all devices support OpenGL ES 2.0. An app can query the OpenGL ES version string and extension string to determine whether the current device supports the features it needs. For information on how to perform this query, see the description of {@code glGetString()} in the OpenGL specification.
Additionally, you must put a {@code <uses-feature>} tag in your manifest file to indicate which version of OpenGL ES your application requires. For more information about the OpenGL ES settings for {@code <uses-feature>}, see OpenGL ES.
The hello-gl2 sample application provies a basic example of how to use OpenGL ES 2.0 with the NDK.
The EGL APIs are only available starting from API level 9. You can, however, use the VM to perform some of the operations that you would get from those APIs. These operations include surface creation and flipping. For an example of how to use {@code GLSurfaceView}, see Introducing GLSurfaceView.
Note: The Android emulator does not support OpenGL ES 2.0 hardware emulation. Running and testing code that uses this API requires a real device with hardware that can support OpenGL ES 2.0.
The NDK provides the following APIs for developing native code that runs on Android 2.2 system images and above.
The {@code jnigraphics} library exposes a C-based interface that allows native code to reliably access the pixel buffers of Java bitmap objects. The workflow for using {@code jnigraphics} is as follows:
To use {@code jnigraphics}, include the {@code <bitmap.h>} header in your source code, and link against {@code jnigraphics} by including the following line in your {@code Android.mk} file:
LOCAL_LDLIBS += -ljnigraphics
Additional details about this feature are in the comments of the {@code bitmap.h} file.
The NDK provides the following APIs for developing native code that runs on Android 2.3 system images and above.
EGL provides a native platform interface for allocating and managing OpenGLES surfaces. For more information about its features, see EGL Native Platform Interface.
EGL allows you to perform the following operations from native code:
The following headers provide EGL functionality:
To link against the system's EGL library, add the following line to your {@code Android.mk} file:
LOCAL_LDLIBS += -lEGL
Android native audio handling is based on the Khronos Group OpenSL ES 1.0.1 API.
The standard OpenSL ES headers {@code OpenSLES.h} and {@code OpenSLES_Platform.h} contain the declarations necessary for performing audio input and output from the native side of Android. The NDK distribution of the OpenSL ES also provides Android-specific extensions. For information about these extensions, see the comments in {@code OpenSLES_Android.h} and {@code OpenSLES_AndroidConfiguration.h}.
The system library {@code libOpenSLES.so} implements the public native audio functions. Link against it by adding the following line to your {@code Android.mk} file:
LOCAL_LDLIBS += -lOpenSLES
For more information about the OpenSL ES API, refer to {@code $NDK/docs/Additional_library_docs/opensles/index.html}, where {@code $NDK} is your NDK installation root directory.
Starting from API level 9, you can write an entire Android app with native code, without using any Java.
Note: Writing your app in native code is not, in itself, enough for your app to run in the VM. Moreover, your app must still access most features of the Android platform via JNI.
This release provides the following native headers:
For more information about these headers, see the NDK API Reference documentation, as well as the comments in the headers, themselves. Also, for more information about the larger topic of writing native apps, see Native Activities and Applications.
When you include one or more of these headers, you must also link against the {@code libandroid.so} library. To link against {@code libandroid.so}, include the following line in your {@code Android.mk} file:
LOCAL_LDLIBS += -landroid
The NDK provides the following APIs for developing native code that runs on Android 4.0 system images and above.
Android native multimedia handling is based on Khronos Group OpenMAX AL 1.0.1 API.
The standard OpenMAX AL headers {@code <OMXAL/OpenMAXAL.h>} and {@code <OMXAL/OpenMAXAL_Platform.h>} contain the declarations necessary for performing multimedia output from the native side of Android.
The NDK distribution of OpenMAX AL also provides Android-specific extensions. For information about these extensions, see the comments in {@code OpenMAXAL_Android.h}.
The system library {@code libOpenMAXAL.so} implements the public native multimedia functions. To link against this library, include the following line in your {@code Android.mk} file:
LOCAL_LDLIBS += -lOpenMAXAL
For more information about this topic, see {@code $NDK/docs/openmaxal/index.html}, where {@code $NDK} is the root directory of your NDK installation.
OpenSL ES support for this Android API level adds PCM support. For more information about OpenSL ES support in the NDK, see OpenSL ES.
The NDK provides the following APIs for developing native code that runs on Android 4.3 system images and above.
The standard OpenGL ES 3.0 headers {@code gl3.h} and {@code gl3ext.h} contain the declarations needed for performing OpenGL ES 3.0 rendering calls from native code. These rendering calls provide the ability to use the GLSL language to define and use vertex and fragment shaders.
To use OpenGL ES 3.0, link your native module against {@code /system/lib/libGLESv3.so} by including the following line in your {@code Android.mk} file:
LOCAL_LDLIBS := -lGLESv3
Not all devices support OpenGL ES 3.0. An app can query the OpenGL ES version string and extension string to determine whether the current device supports the features it needs. For information on how to perform this query, see the description of {@code glGetString()} in the OpenGL specification.
Additionally, you must put a {@code <uses-feature>} tag in your manifest file to indicate which version of OpenGL ES your application requires. For more information about the OpenGL ES settings for {@code <uses-feature>}, see OpenGL ES.
The gles3jni sample application provides a basic example of how to use OpenGL ES 3.0 with the NDK.
Note: The Android emulator does not support OpenGL ES 3.0 hardware emulation. Running and testing code that uses this API requires a real device with hardware that can support OpenGL ES 3.0.
The NDK provides the following APIs for developing native code that runs on Android 4.3 system images and above.
The standard OpenGL ES 3.1 headers {@code gl31.h} and {@code gl3ext.h} contain the declarations needed for performing OpenGL ES 3.1 rendering calls from native code. These rendering calls provide the ability to use the GLSL language to define and use vertex and fragment shaders.
To use OpenGL ES 3.1, link your native module against {@code /system/lib/libGLESv3.so} by including the following line in your {@code Android.mk} file:
LOCAL_LDLIBS := -lGLESv3
Not all devices support OpenGL ES 3.1. An app can query the OpenGL ES version string and extension string to determine whether the current device supports the features it needs. For information on how to perform this query, see the description of {@code glGetString()} in the OpenGL specification.
Additionally, you must put a {@code <uses-feature>} tag in your manifest file to indicate which version of OpenGL ES your application requires. For more information about the OpenGL ES settings for {@code <uses-feature>}, see OpenGL ES.
The gles3jni sample application provides a basic example of how to use OpenGL ES 3.1 with the NDK.
Note: The Android emulator does not support OpenGL ES 3.1 hardware emulation. Running and testing code that uses this API requires a real device with hardware that can support OpenGL ES 3.1.