android_studio_logo Android Studio

Use can use Conan to cross-build your libraries for Android in different architectures. If you are using Android Studio for your Android application development, you can integrate it conan to automate the library building for the different architectures that you want to support in your project.

Here is an example of how to integrate the libpng conan package library in an Android application, but any library that can be cross-compiled to Android could be used using the same procedure.

We are going to start from the “Hello World” wizard application and then will add it the libpng C library:

  1. Create a new Android Studio project and include C++ support.


2 Select your API level and target.


  1. Add an empty Activity and name it.

wizard3 wizard4

  1. Select the C++ Standard


5. Change to the project view and in the app folder create a conanfile.txt and conan_android_profile files with the following contents:







# Linux:
# Windows:
# android-toolchain:ndk_path=~/AppData/local/Android/Sdk/ndk-bundle
# OSX:
# android-toolchain:ndk_path=~/Library/Android/sdk/ndk-bundle


You need to adjust the android-toolchain:ndk_path variable in the [options] section to point to the Android NDK installed by your Android Studio. It’s usually downloaded in the first project build. The default paths for the NDK are:

  • Linux: ~/Android/Sdk/ndk-bundle
  • Windows: ~/AppData/local/Android/Sdk/ndk-bundle
  • OSX: ~/Library/Android/sdk/ndk-bundle

We are using the build_requires feature to include the recipe android-toolchain/r13b@lasote/testing. That recipe will create a specific toolchain for our settings and will prepare some environment variables (CC, CXX, PATH, CONAN_CMAKE_FIND_ROOT_PATH…) and propagate some c/cpp flags. It allows to automatically prepare your build system to use the Android toolchain and cross-build the libraries from the [requires] section of the conanfile.txt file for the Android operating system. All in a transparent manner.

Once our [requires] are built, the android-toolchain recipe it not used anymore.

  1. Open the CMakeLists.txt file from the app folder and replace the contents with:
cmake_minimum_required(VERSION 3.4.1)


add_library(native-lib SHARED src/main/cpp/native-lib.cpp)
target_link_libraries(native-lib ${CONAN_LIBS})

7. Open the build.gradle file, we are configuring the architectures we want to build specifying the abiFilters, and adding a new task conanInstall that will call conan install command for every architecture we have specified in the abiFilters:


build.gradle, in the defaultConfig section, append:

ndk {
   // Specifies the ABI configurations of your native
   // libraries Gradle should build and package with your APK.
   abiFilters 'armeabi-v7a', 'x86', 'armeabi' // 'arm64-v8a', mips', ‘x86_64’

build.gradle, after the android block:

task conanInstall {
   def CONAN_ARCHS_MAP = ["armeabi-v7a":'armv7', "armeabi":'armv6', "arm64-v8a": "armv8"]
   def api_level = android.defaultConfig.minSdkVersion.mApiLevel
   android.defaultConfig.ndk.abiFilters.each {
       def arch = CONAN_ARCHS_MAP.get(it, it)
       def build_dir = new File("app/conan/$it")
       // if you have problems running the command try to specify the absolute
       // path to conan (Known problem in MacOSX)
       def cmd = "conan install --file ../../conanfile.txt " +
               "--profile ../../conan_android_profile " + // base android profile
               "-s arch=${arch} -s os.api_level=${api_level} " + // Adjust api level and architecture
               " --build missing " // Build from sources automatically if needed.
       print(">> ${cmd} \n")

       def sout = new StringBuilder(), serr = new StringBuilder()
       def proc = cmd.execute(null, build_dir)
       proc.consumeProcessOutput(sout, serr)
       println "$sout $serr"
       if(proc.exitValue() != 0){
           throw new Exception("out> $sout err> $serr" + "\nCommand: ${cmd}")
  1. Finally open the default example cpp library in app/src/main/cpp/native-lib.cpp and include some lines using your library. Be careful with the JNICALL name if you used other app name in the wizard:
#include <jni.h>
#include <string>
#include "png.h"
#include "zlib.h"
#include <sstream>
#include <iostream>

extern "C"
       JNIEnv *env,
       jobject /* this */) {
   std::ostringstream oss;
   oss << "Compiled with libpng: " << PNG_LIBPNG_VER_STRING << std::endl;
   oss << "Running with libpng: " << png_libpng_ver << std::endl;
   oss << "Compiled with zlib: " << ZLIB_VERSION << std::endl;
   oss << "Running with zlib: " << zlib_version << std::endl;

   return env->NewStringUTF(oss.str().c_str());

Build your project normally, conan will create a “conan” folder with a folder for each different architecture you have speified in the abiFilters with a conanbuildinfo.cmake file.

Then run the app using an x86 emulator for best performance:


See also

Check the section howtos/Cross building/Android to read more about cross building for Android.