android - Using armeabi and armeabi-v7a libraries with APK splits -

android - Using armeabi and armeabi-v7a libraries with APK splits -

i've been using new apk splits feature of 0.13 plugin android , managed halve size of of build scripts , speed builds factor of 4x. app has bit more 20mb worth of libraries each platform , keeping apk size little priority. before 0.13 had couple of scripts dynamically staged .so files in right build folders (depending on platform building for) , executed total build. worked fine terribly slow , involved unfortunate mix of gradle , non-gradle scripts.

the latest apk splits feature solved of woes i'm still having problem armeabi-v7a libraries. seems when gradle builds armeabi-v7a flavor, looks libraries defined in /libs/armeabi-v7a folder , ignores libraries compiled armeabi not armeabi-v7a.

for example, 1 of apps:

app1/ - libs - armeabi - lib1.so - lib2.so - lib3.so - armeabi-v7a - lib3.so - x86 - lib1.so - lib2.so - lib3.so

when compile armeabi-v7a gradle includes armeabi-v7a/lib3.so not armeabi/lib1.so , armeabi/lib2.so. @ runtime, apk doesn't work (obviously) because can't find lib1.so , lib2.so.

is there way tell gradle add together libraries found in armeabi/ not in armeabi-v7a/ armeabi-v7a apks?

i opened issue b.android.com (see https://code.google.com/p/android/issues/detail?id=77490) , it's known limitation in 0.13+. it'll fixed soon.

android gradle apk android-gradle