| commit | f58fd52b1435b87b11539ab792b7651d10801231 | [log] [tgz] |
|---|---|---|
| author | Jiyong Park <jiyong@google.com> | Fri May 01 10:29:09 2020 +0900 |
| committer | Baligh Uddin <baligh@google.com> | Fri May 01 13:13:13 2020 +0000 |
| tree | bb65c15961004184eb014b51214a6df2b0dfbeb4 | |
| parent | 345baa7c98591766878e02a4546ded4a0c262e38 [diff] |
Stem names are used in apkcerts.txt _apkcerts_write_line has assumed that the stem name of a package is the same as the module of it. That assumption however breaks for APK-in-APEX, in which case the stem name is Foo while the module name is Foo.com.android.bar (where com.android.bar is the name of the APEX where the APK is in). Fixing the issue by recording the stem name and use it. Bug: 155440232 Test: OVERRIDE_TARGET_FLATTEN_APEX=true m apkcerts-list and check the generat4ed apkcerts txt file to see that it has Tethering.apk instead of Tethering.com.android.tethering.apex Change-Id: I56bc55e2231eb946617a9d6f97d55c9b61f3bff7
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.