| commit | b35231ece0dda829187ee3688d0b6ef8f3ff755c | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Wed Aug 30 15:57:16 2023 -0700 |
| committer | Cole Faust <colefaust@google.com> | Wed Aug 30 17:17:19 2023 -0700 |
| tree | 90863b94ed71a3e65ad727dea7d349c95dd3be85 | |
| parent | 401be560de67a16892620282e303b19486f87b51 [diff] |
Build the proguard dict zip without PACKAGING intermediates Before, as each module was built, it would dump its proguard-related files into the PACKAGING folder. Then the rule for the final distable zip would zip up this whole folder. This means that if you built a module that was not part of the system, and then rebuilt the final zip, it would erronously include more proguard files than necessary. This problem was worked around by relying on CI to run `m installclean` every time. Now, the zip proguard files always include the same information. This also makes it so that when you build a module, its proguard files are not copied to the PACKAGING folder, making builds that don't build the final proguard zips slightly faster. Bug: 205632228 Test: diff'd proguard-dict.zip, proguard-dict-mapping.textproto, and proguard-usage.zip before/after this cl on sdk_phone_x86_64. They have diffs, but only in the order of files / lines. Change-Id: I98c02e1eb117c337ba9b98f04ad486597eb9bb86
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.