diff options
author | Steven Moreland <smoreland@google.com> | 2017-04-11 17:36:57 -0700 |
---|---|---|
committer | Steven Moreland <smoreland@google.com> | 2017-04-12 00:37:37 +0000 |
commit | 95df2d370f0ed7e54fa4c3636a7fbb18e73789cc (patch) | |
tree | 8c12f0e9dd2e0426d5ab63a4df50d0f4214af4ff /libhidlmemory | |
parent | 8105d4205b1846eff2719a9f39b1f22b62a67466 (diff) | |
download | libhidl-95df2d370f0ed7e54fa4c3636a7fbb18e73789cc.tar.gz |
Mark libhidlmemory 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 libhwbinder
Test: attempt to compile with BOARD_VNDK_VERSION := current
Change-Id: Id2dfdb40fdbce160cb2262bbdac072ed08de651e
Diffstat (limited to 'libhidlmemory')
-rw-r--r-- | libhidlmemory/Android.bp | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/libhidlmemory/Android.bp b/libhidlmemory/Android.bp index 2b47483..79ec4bc 100644 --- a/libhidlmemory/Android.bp +++ b/libhidlmemory/Android.bp @@ -14,6 +14,7 @@ cc_library_shared { name: "libhidlmemory", + vendor_available: true, cflags: libhidl_flags, shared_libs: [ "libbase", |