summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSteven Moreland <smoreland@google.com>2017-04-13 14:00:54 -0700
committerSteven Moreland <smoreland@google.com>2017-04-19 22:45:42 +0000
commitdefabfc078080d60369d901d3c7662f05605cb29 (patch)
treeb36d244e14a84793e6d9c30cf67d8218c437d68c
parentd7b034fc382d3b76924e2b95da03c026dbbbd35a (diff)
downloadlibnl-defabfc078080d60369d901d3c7662f05605cb29.tar.gz
libnl: 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: m -j libnl Test: attempt to compile with BOARD_VNDK_VERSION := current (cherry picked from commit ed86cb711aae2ac0847ed90d43c187be812f3769) Merged-In: I84c5f871cba9c0e67350e04f5e9f34489470f34e Change-Id: I84c5f871cba9c0e67350e04f5e9f34489470f34e
-rw-r--r--Android.bp1
1 files changed, 1 insertions, 0 deletions
diff --git a/Android.bp b/Android.bp
index 9013201c..53828f63 100644
--- a/Android.bp
+++ b/Android.bp
@@ -1,6 +1,7 @@
cc_library {
name: "libnl",
+ vendor_available: true,
srcs: [
"lib/cache.c",