summaryrefslogtreecommitdiffstats
path: root/libutils
diff options
context:
space:
mode:
authorSteven Moreland <smoreland@google.com>2017-04-11 12:43:16 -0700
committerSteven Moreland <smoreland@google.com>2017-04-12 08:59:41 -0700
commit48cdaff063e9aff3bc8634ee34ab5683bd326fc0 (patch)
treeb118e3deb185fdc949e89a4a5cb5efe7713acfd6 /libutils
parent72ca48e5cbbf557778a417b2109ef560c70d3b8e (diff)
downloadcore-48cdaff063e9aff3bc8634ee34ab5683bd326fc0.tar.gz
core-48cdaff063e9aff3bc8634ee34ab5683bd326fc0.tar.bz2
core-48cdaff063e9aff3bc8634ee34ab5683bd326fc0.zip
libutils: 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: m -j libutils Test: attempt to compile with BOARD_VNDK_VERSION := current Change-Id: I6c1279a74ef071851401e38bbdd377f13827694c
Diffstat (limited to 'libutils')
-rw-r--r--libutils/Android.bp2
1 files changed, 2 insertions, 0 deletions
diff --git a/libutils/Android.bp b/libutils/Android.bp
index 2b7412b4c..b46ad6226 100644
--- a/libutils/Android.bp
+++ b/libutils/Android.bp
@@ -14,6 +14,7 @@
cc_library_headers {
name: "libutils_headers",
+ vendor_available: true,
host_supported: true,
export_include_dirs: ["include"],
target: {
@@ -28,6 +29,7 @@ cc_library_headers {
cc_library {
name: "libutils",
+ vendor_available: true,
host_supported: true,
srcs: [