summaryrefslogtreecommitdiff
path: root/libcutils/socket_local_server_unix.cpp
diff options
context:
space:
mode:
authorSteven Moreland <smoreland@google.com>2017-04-13 15:13:57 -0700
committerSteven Moreland <smoreland@google.com>2017-04-19 10:32:47 -0700
commitd10a02320821c00f849a2a6954d714669a8fe402 (patch)
treea220dd98341dc37d2efae3742a907302c478eb76 /libcutils/socket_local_server_unix.cpp
parent385fe692cccce3a00534bd3b20c471f62fadcd4d (diff)
libbase: 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 libbase Test: build with BOARD_VNDK_VERSION := current (cherry picked from commit c28517f95611c96628e27eb570ff1c2805cbd5f6) Merged-In: I720a00deada4e62628e6fbc4ac830265de9c669f Change-Id: I720a00deada4e62628e6fbc4ac830265de9c669f
Diffstat (limited to 'libcutils/socket_local_server_unix.cpp')
0 files changed, 0 insertions, 0 deletions