Add android toolchains about polly HOT 19 CLOSED

Initial android-cmake toolchain pushed to polly/android branch as-is to get things going.

from polly.

Thanks, merged e670b4c

from polly.

OpenCV Android toolchain: https://github.com/Itseez/opencv/blob/master/platforms/android/android.toolchain.cmake

from polly.

After looking at the diff, that seems to be a better starting point. I'll
move the other one aside to serve as a reference and add the latest android
toolchain from OpenCV. It appears to be identical but with a few small
updates.

#    LIBRARY_OUTPUT_PATH_ROOT should be set in cache to determine where
Android
#    libraries will be installed.
#    Default is ${CMAKE_SOURCE_DIR}, and the android libs will always be
#    under the ${LIBRARY_OUTPUT_PATH_ROOT}/libs/${ANDROID_NDK_ABI_NAME}
#    (depending on the target ABI). This is convenient for Android
packaging.

On Mon, May 4, 2015 at 12:42 PM, Ruslan Baratov [email protected]
wrote:

OpenCV Android toolchain:
https://github.com/Itseez/opencv/blob/master/platforms/android/android.toolchain.cmake

—
Reply to this email directly or view it on GitHub
#10 (comment).

from polly.

https://github.com/taka-no-me/android-cmake

from polly.

CMake target properties:

• ANDROID_GUI
• ANDROID_API_MIN
• ANDROID_API

from polly.

Hello world sample: https://github.com/Discordia/android-cmake/tree/master/samples/hello-android-cmake

from polly.

one more example: https://github.com/Discordia/android-cmake-example

from polly.

Merge f930e10 allows the toolchain to be used with hunter.

However there are still a few bits missing for the toolchain file in general:
Once the STL implementation is chosen, its lib directory is not added to the ANDROID_LINKER_FLAGS nor the linking flags to link to the library.

I updated on my repo a fix for this: f85df73 by creating an ANDROID_STL_LIB_DIR and adding it to the ANDROID_LINKER_FLAGS if gnustl_static is chosen, but would be nice to hear from whoever uses other options for ANDROID_STL on a better solution to deal with this.

ping @headupinclouds

EDIT: Maybe it is a bad idea to hardwire the ANDROID_STL on the ANDROID_LINKER_FLAGS (ANDROID_LINKER_FLAGS sets the value for CMAKE_EXE_LINKER_FLAGS, CMAKE_SHARED_LINKER_FLAGS and CMAKE_STATIC_LINKER_FLAGS) but ANDROID_STL_LIB_DIR should be useful to know where the directory of the lib for the chosen STL is.

from polly.

I've removed Android*.cmake from Polly (31dcb9d) since it's not toolchain related stuff.

Can be used by Hunter: https://github.com/ruslo/hunter/wiki/pkg.android.modules

from polly.

@headupinclouds f89ebf3 I think https://github.com/taka-no-me/android-cmake is the original repo so probably version from OpenCV is older. So I guess we can move android.toolchain.cmake.origin back and remove android.toolchain.cmake (?)

from polly.

@ruslo Agreed. It looks like the taka-no-me repository is actively being updated ("authored 10 days ago"). I like the idea of using this one, since it will probably be easier to push and pull changes from upstream as needed.

from polly.

I've added android-ndk-r10e toolchain: https://github.com/ruslo/polly/wiki/Toolchain-list#android-ndk-xxx

Switch between different ndk versions was made similar to iOS way. You can set different ANDROID_NDK_xxx environment variables and build.py will pick the right version and add ANDROID_NDK CMake variable.

Simple examples compile fine: https://github.com/ruslo/polly/tree/master/examples

from polly.

Guys, if you are going to revert to that toolchain, please be sure that it sets CMAKE_AR CMAKE_ANDROID_API

And be aware that CMAKE_FORCE_C_COMPILER( "${CMAKE_C_COMPILER}" GNU ) sets the forced compiler which makes hunter fail.

from polly.

Guys, if you are going to revert to that toolchain, please be sure that it sets CMAKE_AR CMAKE_ANDROID_API

I'm planning to cherry-pick your changes

from polly.

Sorry, I didn't mean CMAKE_AR, make sure it sets CMAKE_C_PROCESSOR is what I meant - sorry, I wrote it in a hurry.

Anyway, as discussed in #16 (comment) it makes sense that these changes go to upstream and be reviewed by people who have been maintaining this file longer.

from polly.

This has been taken care of with the following pull request: taka-no-me/android-cmake#53

from polly.

Usage example: https://github.com/forexample/android-cmake

from polly.

Well, looks like there is no need to create APK to run executable on device. It's possible to create simple console application and run it using adb shell. So it's easy to orginize testing with CMake's add_test:

• New function android_add_test in Android-Apk project
• Usage example

from polly.