diff options
| author | Inseob Kim <inseob@google.com> | 2019-02-08 21:00:45 +0900 |
|---|---|---|
| committer | Inseob Kim <inseob@google.com> | 2019-02-13 23:32:51 +0000 |
| commit | c0907f191a6c466d077030500f855cdd87ec954a (patch) | |
| tree | 18b82c6ebe4f81d49eb8f34a548d8ecddef7ac47 /cc/coverage.go | |
| parent | 58b31ad33a8df9f8ea27b9d6c928560d7a6a2452 (diff) | |
| download | android_build_soong-c0907f191a6c466d077030500f855cdd87ec954a.tar.gz android_build_soong-c0907f191a6c466d077030500f855cdd87ec954a.tar.bz2 android_build_soong-c0907f191a6c466d077030500f855cdd87ec954a.zip | |
Create sysprop_library soong module
A newly introduced sysprop_library soong module will generate a
java_sdk_library and a cc_library from .sysprop description files.
Both Java modules and C++ modules can link against sysprop_library
module, thus giving consistency for using generated sysprop API.
As Java controls accessibility of Internal / System properties with
@hide and @SystemApi, 2 different header files will be created. And
build system will selectively expose depending on the property owner
and the place where the client libraries go into.
Bug: 80125326
Bug: 122170616
Test: 1) Create sysprop_library module.
Test: 2) Create empty txt files under prebuilts/sdk.
Test: 3) Create api directory, make update-api, and see changes.
Test: 4) Try to link against sysprop_library with various clients.
Test: 5) Soc_specific, Device_specific, Product_specific, recovery flags
work as intended.
Change-Id: I78dc5780ccfbb4b69e5c61dec26b94e92d43c333
Diffstat (limited to 'cc/coverage.go')
0 files changed, 0 insertions, 0 deletions