summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSteven Moreland2017-04-13 16:29:58 -0500
committerSteven Moreland2017-04-19 12:32:45 -0500
commit385fe692cccce3a00534bd3b20c471f62fadcd4d (patch)
tree97479d4978ca85eabfab712268ac102be6f1fae2 /libcutils/Android.bp
parentbb11af88e234f27c08499994f23994289077f5c1 (diff)
downloadplatform-system-core-385fe692cccce3a00534bd3b20c471f62fadcd4d.tar.gz
platform-system-core-385fe692cccce3a00534bd3b20c471f62fadcd4d.tar.xz
platform-system-core-385fe692cccce3a00534bd3b20c471f62fadcd4d.zip
libcutils: 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 libcutils Test: attempt to compile with BOARD_VNDK_VERSION := current Test: (sanity) boot internal marlin (cherry picked from commit 9610c548a8e9018ecdfbe3d7204e8fd70d2554fc) Merged-In: I76f9b28ef08a26d84d1365881e00696cc1dcfe5d Change-Id: I76f9b28ef08a26d84d1365881e00696cc1dcfe5d
Diffstat (limited to 'libcutils/Android.bp')
-rw-r--r--libcutils/Android.bp11
1 files changed, 5 insertions, 6 deletions
diff --git a/libcutils/Android.bp b/libcutils/Android.bp
index 0a3bab744..58170ec71 100644
--- a/libcutils/Android.bp
+++ b/libcutils/Android.bp
@@ -30,16 +30,14 @@ libcutils_nonwindows_sources = [
30] 30]
31 31
32cc_library_headers { 32cc_library_headers {
33 name: "libcutils_vndk_headers",
34 host_supported: true,
35 export_include_dirs: ["include_vndk"],
36}
37
38cc_library_headers {
39 name: "libcutils_headers", 33 name: "libcutils_headers",
34 vendor_available: true,
40 host_supported: true, 35 host_supported: true,
41 export_include_dirs: ["include"], 36 export_include_dirs: ["include"],
42 target: { 37 target: {
38 vendor: {
39 export_include_dirs: ["include_vndk"],
40 },
43 linux_bionic: { 41 linux_bionic: {
44 enabled: true, 42 enabled: true,
45 }, 43 },
@@ -51,6 +49,7 @@ cc_library_headers {
51 49
52cc_library { 50cc_library {
53 name: "libcutils", 51 name: "libcutils",
52 vendor_available: true,
54 host_supported: true, 53 host_supported: true,
55 srcs: [ 54 srcs: [
56 "config_utils.c", 55 "config_utils.c",