Status Update
No update yet.
Comments
ch...@google.com
can you share your android studio version
vh...@google.com
[Deleted User] <[Deleted User]>
Is this happening with Studio 3.0?
[Deleted User] <[Deleted User]>
Note: This worked for me on Windows 7 Pro 32-bit (with Android Studio 2.3.3). Seems like an issue with adt-branding module (which should contain the "/idea/AndroidStudioApplicationInfo.xml" resource).
jo...@google.com
Hi, also happened on Mac Book Pro 15 retina mi-2015
MacOs Sierra 10.12.6
Android Studio 2.3.3
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
MacOs Sierra 10.12.6
Android Studio 2.3.3
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)
ik...@gmail.com
Thank you for this feedback. Your feedback helps make sure Android development tools are great! Given your issues has been resolved I am closing this issue.
[Deleted User] <[Deleted User]>
Any idea how soon the next preview release will be, such that we can see the fixes to this and other issues?
[Deleted User] <[Deleted User]>
@#8 - I don't think so - I tried over the weekend to get 2.2p2 to pick up the Application.mk to no avail.
ks...@google.com
Sorry! This is included in preview 3, which we expect to be going out in the very near future. I'm hesitant to give an exact date for fear of jinxing the release, but you should have a fix soon.
sa...@dinoz.mobi
Will we have access to any documentation on how to specify the Application.mk path?
sa...@gmail.com
In the mean while, easy fiddle with ndk_build script seems to be enough.
gr...@kochaniak.com
Same issue as #6 comment, with Android Studio 2.2 Preview 5. I'm trying to build an x86 and armabi-v7a, but using a pre-built shared library, and ndk-build complains about missing arm64-v8a .so etc. All my Application.mk files do specify 'APP_ABI := x86 armeabi-v7a' only. And in the External Build Output I do see:
Error while executing 'C:\android\android-sdk\ndk-bundle\ndk-build.cmd' with arguments {NDK_PROJECT_PATH=null APP_BUILD_SCRIPT=C:\android\TtsNativeLib\jni\Android.mk NDK_APPLICATION_MK=C:\android\TtsNativeLib\jni\Application.mk APP_ABI=arm64-v8a NDK_ALL_ABIS=arm64-v8a NDEBUG=1 APP_PLATFORM=android-21 NDK_OUT=C:\android\TtsNativeLib\build\intermediates\ndkBuild\debug\obj NDK_LIBS_OUT=C:\android\TtsNativeLib\build\intermediates\ndkBuild\debug\lib -n}
It does try to build unwanted ABIs.
Error while executing 'C:\android\android-sdk\ndk-bundle\ndk-build.cmd' with arguments {NDK_PROJECT_PATH=null APP_BUILD_SCRIPT=C:\android\TtsNativeLib\jni\Android.mk NDK_APPLICATION_MK=C:\android\TtsNativeLib\jni\Application.mk APP_ABI=arm64-v8a NDK_ALL_ABIS=arm64-v8a NDEBUG=1 APP_PLATFORM=android-21 NDK_OUT=C:\android\TtsNativeLib\build\intermediates\ndkBuild\debug\obj NDK_LIBS_OUT=C:\android\TtsNativeLib\build\intermediates\ndkBuild\debug\lib -n}
It does try to build unwanted ABIs.
sa...@dinoz.mobi
I was able to prevent it from building unwanted ABIs using this config:
defaultConfig {
ndkBuild {
abiFilters "armeabi-v7a", "x86"
}
}
defaultConfig {
ndkBuild {
abiFilters "armeabi-v7a", "x86"
}
}
sa...@gmail.com
Application.mk is now picked up from the jni directory automatically. It is also possible to add non-standard path with
arguments "NDK_APPLICATION_MK=./test/mk/Application.mk"
arguments "NDK_APPLICATION_MK=./test/mk/Application.mk"
Description
This means that projects that use a non-default STL or toolchain will fail to build. There also seems to be no way of configuring C++ STL version or toolchain version in this case either.
Gradle plugin should allow specification of `Application.mk` inside the `externalNativeBuild > ndkBuild` block and pass it on as NDK_APP_APPLICATION_MK build variable.
This issue was tested with Android Studio 2.2 Preview 1 and Gradle plugin 2.2.0-alpha1.