aboutsummaryrefslogtreecommitdiff
path: root/googlemock
diff options
context:
space:
mode:
authorDan Willemsen <dwillemsen@google.com>2017-04-07 14:11:05 -0700
committerDan Willemsen <dwillemsen@google.com>2017-04-10 18:03:55 -0700
commitbff63a6026b1e6c1326ca2cb0183b6eb53dd3358 (patch)
tree27654a3a42e8292d780fae503c55d43c9ed4ab28 /googlemock
parent6cac0f7aa63de86680dcaff783f53c26cc5a34f8 (diff)
downloadgoogletest-bff63a6026b1e6c1326ca2cb0183b6eb53dd3358.tar.gz
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 Change-Id: I9722ac3b803d9dab8c01a714d72904fa4dd40196
Diffstat (limited to 'googlemock')
-rw-r--r--googlemock/Android.bp2
1 files changed, 2 insertions, 0 deletions
diff --git a/googlemock/Android.bp b/googlemock/Android.bp
index 0f2f9e5f..337c0540 100644
--- a/googlemock/Android.bp
+++ b/googlemock/Android.bp
@@ -61,6 +61,7 @@ cc_library_static {
srcs: ["src/gmock-all.cc"],
rtti: true,
static_libs: ["libgtest"],
+ vendor_available: true,
}
cc_library_static {
@@ -68,6 +69,7 @@ cc_library_static {
defaults: ["gmock_defaults", "gmock_flags"],
srcs: ["src/gmock_main.cc"],
static_libs: ["libgtest"],
+ vendor_available: true,
}
// Deprecated: use libgmock instead