From 4cef24ee3c034fca86147062e9045b7e9e0dc27f Mon Sep 17 00:00:00 2001 From: Dan Willemsen Date: Fri, 7 Apr 2017 14:12:18 -0700 Subject: 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: 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: I5aa9e3463c53a2c13110d6fffb61a2bbc09892f2 --- Android.bp | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Android.bp b/Android.bp index bb120a7d9..17942821d 100644 --- a/Android.bp +++ b/Android.bp @@ -16,8 +16,9 @@ // host + device static lib cc_library_static { - host_supported: true, name: "libc++_static", + host_supported: true, + vendor_available: true, clang: true, srcs: [ "src/algorithm.cpp", @@ -72,8 +73,9 @@ cc_library_static { // host + device dynamic lib cc_library_shared { - host_supported: true, name: "libc++", + host_supported: true, + vendor_available: true, clang: true, whole_static_libs: ["libc++_static"], stl: "none", -- cgit v1.2.3