diff options
| author | 2017-06-23 19:24:43 +0900 | |
|---|---|---|
| committer | 2017-07-18 14:48:29 +0900 | |
| commit | 8effde47def8609b08be27f75d9f24f8b943e3ed (patch) | |
| tree | 223d67bd1a21ad363ba8eec952cbb1b24cc85b83 /python/python_test.go | |
| parent | da4a7257b5b4c4fd41b8e8e084713e3e4f20187b (diff) | |
Install VNDK libs in /system instead of /vendor
If BOARD_VNDK_VERSION is set, and a module is set to
`vendor_available: true` it is installed in /system and /vendor.
However, if the module is a VNDK library, it must be
installed at `/system/${LIB}/vndk` instead of /vendor/${LIB}.
For those modules, need following to set.
vendor_available: true,
vndk: {
enabled: true,
support_system_process: true,
},
`support_system_process` is optional to define.
If it is defined to true, the module is regarded as vndk-sp.
link-type check for VNDK modules is added to make sure that VNDK
modules only link to other VNDK shared libraries or LL-NDKs.
move the ABI checks to VNDK from all of vendor_available.
Bug: 38304436
Test: attempt to compile with BOARD_VNDK_VERSION:=current
Test: Use `vendor_available_vndk: true` for VNDK modules and compile
with BOARD_VNDK_VERSION:=current
Change-Id: I409268e0b7f05a9d01697bf9f9f4726b5aac631f
Diffstat (limited to 'python/python_test.go')
0 files changed, 0 insertions, 0 deletions