Revision history [back]

@berak is right, this issue has been fixed already and new release (3.2) should contain new libpng library without this issue, Android package will be built along with the release. But I can not say concrete date, probably Q4.

You can easily build it under Windows, I think:

• Install cmake, python, Android SDK (don't forget to configure it), Android NDK (recommended r10e, versions >=11 are not supported yet)
• make sure your PATH env variable contains directories with cmake.exe and python.exe
• set ANDROID_SDK and ANDROID_NDK env variables to paths to kits
• run python opencv/platforms/android/build_sdk.py build_dir opencv

Take a look at the commands being run in our nightly Android builds: http://pullrequest.opencv.org/buildbot/waterfall?tag=android_pack

We are actually thinking about freezing OpenCV Manager, because this usage model needs more effort for support.

@berak is right, this issue has been fixed already and new release (3.2) should contain new libpng library without this issue, Android package will be built along with the release. But I can not say concrete date, probably Q4.

You can easily build it under Windows, I think:

• Install cmake, python, Android SDK (don't forget to configure it), Android NDK (recommended r10e, versions >=11 are not supported yet)
• make sure your PATH env variable contains directories with cmake.exe and python.exe
• set ANDROID_SDK and ANDROID_NDK env variables to paths to kits
• run python opencv/platforms/android/build_sdk.py build_dir opencv

Take a look at the commands being run in our nightly Android builds: http://pullrequest.opencv.org/buildbot/waterfall?tag=android_pack

We are actually thinking about freezing OpenCV Manager, Manager package in Google Play, because this usage model needs more effort for support.