diff options
author | Dan Willemsen <dwillemsen@google.com> | 2017-04-07 14:12:51 -0700 |
---|---|---|
committer | Steven Moreland <smoreland@google.com> | 2017-04-11 18:25:24 +0000 |
commit | c86ec64f26681f849282ebd20b5767bf97cecc6b (patch) | |
tree | 64bb0c050c4db9ad9d721e05e3e199bfd02e60b0 | |
parent | c9b51f66c918b8d06bbdd26b60ffbad5063d9348 (diff) | |
download | libevent-c86ec64f26681f849282ebd20b5767bf97cecc6b.tar.gz |
Mark as vendor_availableandroid-vts-8.0_r2android-vts-8.0_r1oreo-dev
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
Merged-In: I3aef3b8f6b7e5eba3e6036a460faf0ca6fc301d3
Change-Id: I3aef3b8f6b7e5eba3e6036a460faf0ca6fc301d3
-rw-r--r-- | Android.bp | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -15,6 +15,7 @@ cc_library { name: "libevent", host_supported: true, + vendor_available: true, unique_host_soname: true, arch: { @@ -30,7 +31,6 @@ cc_library { "-Wno-unused-parameter", "-Werror", ], - local_include_dirs: ["include"], export_include_dirs: ["include"], srcs: [ |