| Age | Commit message (Collapse) | Author |
|---|
|
Test: Build + TH + boot phone & use bluetooth
Bug: 216433795
Change-Id: I7f8f09bb55b66c0bf29cc901cb3b6d6a254bcefd
|
|
Bug: 206121418
Test: Compile
Change-Id: I090af110c1b00b38b10df6a6ac92f5b4d1de936f
|
|
Bug: 187196593
Test: boot
Change-Id: I9d5a1066103ae578fd085d0db2201b4650ca7827
|
|
Added SPDX-license-identifier-BSD to:
Android.bp
Bug: 68860345
Bug: 151177513
Bug: 151953481
Test: m all
Exempt-From-Owner-Approval: janitorial work
Change-Id: Ie16eeafcf0ca2330352b4daabb1525698db691c5
|
|
An NDK built static variant is needed for
clients that build against the NDK.
The new library will not be part of the
NDK public interface.
Bug: 123237859
Test: Camera CTS
Change-Id: I379ce9c27c34d54048f4a0f1c3d0b4fadb6abc7e
|
|
Test: build update_engine_sideload
Change-Id: Ibdf0d789f9cbdfe4c4f8583ee74e835ad2609ee9
|
|
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: Ia48408aa590eb357337c42453939ff43e5d0f42e
|
|
Change-Id: I75cf1cc4fe6abe0967aebefc3c62aad86555a6e3
|
