diff options
| author | 2022-02-04 12:36:33 +0900 | |
|---|---|---|
| committer | 2022-02-04 13:07:14 +0900 | |
| commit | 91f9203af42d029de2e025bcedc1044a4a1e5dcc (patch) | |
| tree | 28faa3c2135b10f52fdfcfae56e53101b74b9a3c /sdk/build_release_test.go | |
| parent | c5a967630ef38406da5143497136e21c356324d5 (diff) | |
VNDK libs use "unique" APEX variants
In case there are two vendor apexes(one with "use_vndk_as_stable:true",
and the other with "use_vndk_as_stable:false") a VNDK lib used by both
will have "APEX" variant and the former APEX will use "apex" variation.
For example,
apex1(use_vndk_as_stable) -> foo -> libvndk
apex2 -> bar -> libvndk
Since foo, bar and libvndk are mutated into two APEX variations("",
"apex10000"), foo will use the apex variation of libvndk.
To fix this, VNDK libs can use "unique" APEX variations. Then, in the
above example, foo will have "myapex1" variation and libvndk will have
two APEX variations("" and "apex2"). So foo will link to ""(non-APEX)
variation as fallback.
Bug: 216847402
Test: m nothing (soong tests)
Change-Id: I116932860ef79e22dc338a58b251e3ca693ab4f3
Diffstat (limited to 'sdk/build_release_test.go')
0 files changed, 0 insertions, 0 deletions