summaryrefslogtreecommitdiffstats
path: root/libbacktrace
diff options
context:
space:
mode:
authorSteven Moreland <smoreland@google.com>2017-04-13 23:35:06 -0700
committerSteven Moreland <smoreland@google.com>2017-04-19 10:32:43 -0700
commitbb11af88e234f27c08499994f23994289077f5c1 (patch)
treec8a1c559682fb41e95dc6d2a1ea7e56c26c9d559 /libbacktrace
parent3c71bbdde3a8d3219934a0fadbfd40b1850a9043 (diff)
downloadcore-bb11af88e234f27c08499994f23994289077f5c1.tar.gz
core-bb11af88e234f27c08499994f23994289077f5c1.tar.bz2
core-bb11af88e234f27c08499994f23994289077f5c1.zip
libbacktrace: make 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: 33241851 Test: build and flash internal marlin Test: m -j libbacktrace Test: build with BOARD_VNDK_VERSION := current (cherry picked from commit 4c0e956c7690abf0c434e742a369fb8576abf413) Merged-In: Idab4880e011416ebc40b225205c30fb5ed8661db Change-Id: Idab4880e011416ebc40b225205c30fb5ed8661db
Diffstat (limited to 'libbacktrace')
-rw-r--r--libbacktrace/Android.bp1
1 files changed, 1 insertions, 0 deletions
diff --git a/libbacktrace/Android.bp b/libbacktrace/Android.bp
index 7de72a876..4a525be97 100644
--- a/libbacktrace/Android.bp
+++ b/libbacktrace/Android.bp
@@ -62,6 +62,7 @@ cc_library_headers {
cc_library {
name: "libbacktrace",
+ vendor_available: true,
defaults: ["libbacktrace_common"],
host_supported: true,