diff options
| author | 2020-03-31 15:31:17 +0900 | |
|---|---|---|
| committer | 2020-04-03 05:57:38 +0000 | |
| commit | ea97f51a2901d1285132f4e7c6ad169e5d68da71 (patch) | |
| tree | 2279f542956dab7f3afb82b32860e1504ff1628c /rust/coverage.go | |
| parent | 1c5d4fe4f7a00d4604e7db3258048e9b3f5878d1 (diff) | |
Don't allow a lib having stubs to become a member of VNDK
If a lib has stubs, that means the library provides stable C APIs and
the APIs are guaranteed to be maintained in a backwards compatible
manner. Then there is no reason to have the same library in VNDK,
because VNDK is for libraries (usually having C++ interfaces) where API
stability across the yearly releases is hard (or impossible) to be
guaranteed.
This change triggers an error when the build system finds a VNDK lib
which has stubs defined. Users are suggested to make the lib an LLNDK
one.
Bug: 151303316
Test: m
Change-Id: Id305196a9d5a6fc7e7f9c02f3fa076859dc9a282
Diffstat (limited to 'rust/coverage.go')
0 files changed, 0 insertions, 0 deletions