summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDan Willemsen <dwillemsen@google.com>2017-04-07 14:15:02 -0700
committerSteven Moreland <smoreland@google.com>2017-04-14 16:42:32 +0000
commit703e783e280b0ce9e8215960dc08b389cf12ed3c (patch)
treec319585e07ff8ed7d3c1c7a7f97da08848880a2d
parent24230cd423d91e45ea76e1bcf66de8e0c26c6fed (diff)
downloadplatform_hardware_libhardware_legacy-703e783e280b0ce9e8215960dc08b389cf12ed3c.tar.gz
platform_hardware_libhardware_legacy-703e783e280b0ce9e8215960dc08b389cf12ed3c.tar.bz2
platform_hardware_libhardware_legacy-703e783e280b0ce9e8215960dc08b389cf12ed3c.zip
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 Bug: 37343006 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 Merged-In: I3f1e4986c5920b4a64768636cb0bc37fa602c7a7 Change-Id: I3f1e4986c5920b4a64768636cb0bc37fa602c7a7
-rw-r--r--Android.bp1
1 files changed, 1 insertions, 0 deletions
diff --git a/Android.bp b/Android.bp
index a24f426..087342a 100644
--- a/Android.bp
+++ b/Android.bp
@@ -6,4 +6,5 @@ cc_library {
srcs: ["power/power.c"],
export_include_dirs: ["include"],
shared_libs: ["libcutils", "liblog"],
+ vendor_available: true,
}