aboutsummaryrefslogtreecommitdiff
path: root/C
diff options
context:
space:
mode:
authorDan Willemsen <dwillemsen@google.com>2017-04-07 14:21:59 -0700
committerDan Willemsen <dwillemsen@google.com>2017-04-10 18:02:14 -0700
commit1054fa132ca6db0edf743fe1b4902dd12895c003 (patch)
tree7c851f7d858d686c10bb3c0ba194082491c2d7cf /C
parenta307a48ab819d1d76e1e3b003594aa6f03b920f5 (diff)
downloadlzma-1054fa132ca6db0edf743fe1b4902dd12895c003.tar.gz
Mark as vendor_available
By setting vendor_available, the following may become true: * a prebuilt library from this release may be used at runtime by in a later releasse (by vendor code compiled against this release). so this library shouldn't depend on runtime state that may change in the future. * this library may be loaded twice into a single process (potentially an old version and a newer version). The symbols will be isolated using linker namespaces, but this may break assumptions about 1 library in 1 process (your singletons will run twice). Background: This means that these modules may be built and installed twice -- once for the system partition and once for the vendor partition. The system version will build just like today, and will be used by the framework components on /system. The vendor version will build against a reduced set of exports and libraries -- similar to, but separate from, the NDK. This means that all your dependencies must also mark vendor_available. At runtime, /system binaries will load libraries from /system/lib*, while /vendor binaries will load libraries from /vendor/lib*. There are some exceptions in both directions -- bionic(libc,etc) and liblog are always loaded from /system. And SP-HALs (OpenGL, etc) may load /vendor code into /system processes, but the dependencies of those libraries will load from /vendor until it reaches a library that's always on /system. In the SP-HAL case, if both framework and vendor libraries depend on a library of the same name, both versions will be loaded, but they will be isolated from each other. It's possible to compile differently -- reducing your source files, exporting different include directories, etc. For details see: https://android-review.googlesource.com/368372 None of this is enabled unless the device opts into the system/vendor split with BOARD_VNDK_VERSION := current. Bug: 36426473 Bug: 36079834 Test: Android-aosp_arm.mk is the same before/after Test: build.ninja is the same before/after Test: build-aosp_arm.ninja is the same before/after Test: attempt to compile with BOARD_VNDK_VERSION := current Change-Id: I7625075aea9c5c8b1ffdc8794776df624365263a
Diffstat (limited to 'C')
-rw-r--r--C/Android.bp1
1 files changed, 1 insertions, 0 deletions
diff --git a/C/Android.bp b/C/Android.bp
index 2c1405b..803ecff 100644
--- a/C/Android.bp
+++ b/C/Android.bp
@@ -3,6 +3,7 @@
cc_library {
name: "liblzma",
host_supported: true,
+ vendor_available: true,
sdk_version: "9",
stl: "none",