diff options
| author | 2024-07-26 19:24:27 +0000 | |
|---|---|---|
| committer | 2024-07-26 19:24:27 +0000 | |
| commit | a8e2d6173d0d83ead3e481124311ab59deced404 (patch) | |
| tree | 100cc766f4c6116cd3173fd8a5f1a840d8d487bf /java/systemserver_classpath_fragment.go | |
| parent | bd0b157c1f8922f2ef1a0d759137a0d2aee5fe11 (diff) | |
Do not rename prebuilt apexes for product packaging
https://r.android.com/2901309 added support for handling installation
rules for multiple prebuilts. One of the implementation details there
was to change LOCAL_MODULE name to the source apex name in the generated
.mk files.
This causes issues in partner builds where the google singed apex
com.google.android.foo gets renamed to com.android.foo in
out/soong/Android-$PRODUCT.mk. If the partner builds does not include
the aosp apex in its PRODUCT_PACAKGES, then the google signed apex gets
elided from packaging.
This CL undoes that change. After this CL, the name of the module as it
appears in Android.bp will match the LOCAL_MODULE name emitted for
product packaging.
Test: in build/soong, go test ./apex
Bug: 355682304
Change-Id: Icadbb75609174cff5326f52baf7d53e901f9f1c0
Diffstat (limited to 'java/systemserver_classpath_fragment.go')
0 files changed, 0 insertions, 0 deletions