diff options
| author | 2022-02-04 11:54:50 +0900 | |
|---|---|---|
| committer | 2022-02-04 13:07:11 +0900 | |
| commit | c5a967630ef38406da5143497136e21c356324d5 (patch) | |
| tree | f175282f76ea16d71c1f3886f4e6c7691f9270c0 /java/bootclasspath_fragment.go | |
| parent | 99a81c8dfd64b10b58bfa6b7ed9bf5597e4489b0 (diff) | |
use_vndk_as_stable APEX shouldn't include VNDK lib
Even though a vendor APEX sets use_vndk_as_stable:true it was possible
to include a VNDK lib by directly depending on it with
native_shared_libs.
But it's contradictory to have a VNDK lib while declaring not to include
VNDK libs. It was missing since pruning dependencies on VNDK libs was
done only for transitive deps.
Added a check to reject this.
Bug: 216847402
Test: m nothing(running soong tests)
Change-Id: I8d79a434b1bfe8e563cf8968fa76830b0e582f66
Diffstat (limited to 'java/bootclasspath_fragment.go')
0 files changed, 0 insertions, 0 deletions