| commit | 5cba391313b3b5f1ff4aee6c31f893426eb52d7a | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Fri May 10 12:41:10 2024 -0700 |
| committer | Cole Faust <colefaust@google.com> | Fri May 10 12:41:10 2024 -0700 |
| tree | 770598e209c80dad6f5abf6eb8896a6434b52b49 | |
| parent | db3606ddd8eb0c1ccd124174b25e608827a12a96 [diff] |
Only consider EXTRA_INSTALL_ZIPS relevant by their primary file Sometimes android_app_bundles exist in the tree but are not added to PRODUCT_PACKAGES, in that case, they shouldn't be added to file_list.txt. We can tell if they're in PRODUCT_PACKAGES by if their primary file is present in the list of files to install. Bug: 337869220 Test: m out/target/product/emu64x/obj/PACKAGING/system_intermediates/file_list.txt and checking it for the extra NetworkStackGoogle apks, with a local NetworkStackGoogle android_app_set added into the tree Change-Id: I22bcd9e972e1c9d5c7ddca788b9c6edc72f0a9dd
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.