OSDN Git Service

Don't extract jni from prebuilt apks.
authorYing Wang <wangying@google.com>
Fri, 1 May 2015 21:02:26 +0000 (14:02 -0700)
committerYing Wang <wangying@google.com>
Fri, 1 May 2015 23:09:58 +0000 (16:09 -0700)
commit3797466fbd31cc3ca5a1eddea64e7fdf0921ea67
tree887ad604498355e96f2287e5d5ab7c28be0ee2d5
parent069f1f8942bf89817b064506495f6ab181548b55
Don't extract jni from prebuilt apks.

- We don't need LOCAL_PAGE_ALIGN_JNI_SHARED_LIBRARIES now, for we always
  page-align jni shared libraries and store them umcompressed.
- For prebuilt apks, we don't extract jni any more; Instead we always run
  uncompress-shared-libs on them.
- For apks built from source, we still install the jni separately, because
  that way multiple apks can share the same jni and it saves space.

With this change, for most prebuilt apks, we don't need to specify
LOCAL_PREBUILT_JNI_LIBS ("@lib/<abi>/foo.so") any more, for the build
system automatically replaces the embedded jni with uncompressed files;
But if a prebuilt is a fat apk (i.e. containing jni not needed by the
current product architecture), you still need LOCAL_PREBUILT_JNI_LIBS to
specify what jni to keep. Otherwise all embedded jni will be replaced with
uncompressed files, that wastes space.

Bug: 8076853
Change-Id: Icf07e0998ac3602e6e05e80fed836fbafca33e01
core/clear_vars.mk
core/definitions.mk
core/install_jni_libs.mk
core/install_jni_libs_internal.mk
core/package_internal.mk
core/prebuilt_internal.mk