Support for Android Studio

[opencv-pushbot]

Transferred from http://code.opencv.org/issues/4366

|| Philipp Hasper on 2015-05-28 11:31
|| Priority: Normal
|| Affected: None
|| Category: android
|| Tracker: Feature
|| Difficulty: 
|| PR: 
|| Platform: None / None

Support for Android Studio

Android Studio is now the official supported way for developing Android apps - the Eclipse integration is deprecated.

We need to migrate the Android tutorials / Android build chain to Android Studio.

History

[PhilLab]

Is this planned for OpenCV 3.0.1?

[hauptmech]

I have been having a very unpleasant experience getting opencv and android development to work. I'm new to android and the java toolchain. I'd be really happy with a commandline walkthrough of getting any opencv native sample running with gradle+ndk-build. An android studio example would be ok too but that seems to be a moving target right now.

[PhilLab]

Yeah, the "these tutorials are for Eclipse but are easily reproducable with Android Studio"-sentence at the beginning of many new Android OpenCV tutorials seems rather cynical 😉 It does work but it is by no means easy if you are new to Gradle.

[hauptmech]

12 hours to get tutorial-2-mixedprocessing to build and run. Having OpenCV 2.4 and an Arm64 device did not help things, but most of my time was figuring out a working combination of android studio, android_ndk, gradle-experimental vs gradle plugins, and viable imports of the samples (or gradle layout remappings).

The most useful thing you guys could do is add gradle files to the samples. At least one could build them and start learning from them then.

[PhilLab]

@hauptmech: is it possible for you to create a pull request containing that?

[hauptmech]

Don't have time. Also anything I came up with would be nothing close to best practice which is what you want for a sample.

You will need to decide whether to support ndk-build or android-studio with gradle-experimental plugin.

[hauptmech]

I revisited the OpenCV samples as prep to tackle the ROS android stuff. Using gradle-experimental and an in-situ build.gradle file for the library worked well for me. Possibly neither are best practice but after a couple days of working with this as a beginner, I can say that this approach is much easier to wrap my head around than the Import-to-android-studio way which has generally unreliable documentation and seems to change every few months.

I jotted down what I did here: http://hauptmech.github.io/OpenCV1/

[PhilLab]

@mshabunin Would this also be an issue for milestone 3.2 ? Maybe the priority could be increased as well - Android Studio is quite mature now.