| commit | 9291155ad04e98bf081a57e806ef71e351eb1f6b | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Fri Feb 21 22:41:50 2025 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Wed Mar 12 23:32:31 2025 +0000 |
| tree | e5d882f9cf76cdb380ccd71edd76ae46282c9812 | |
| parent | 1509ee5ab52f6f07774d651ace44778dc6f0d08d [diff] |
Remove redundant entries from symbols.zip Currently, symbols.zip contains multiple duplicates of the symbols file, which are derived from uninstalled soong modules that produce androidmk entries and share the identical symbols file with the installed modules. These are likely unintended behavior, given that the current build rule of the symbols.zip creates dependency on all generated images instead of all modules that generate the symbols file. This change modifies the build rule of the symbols.zip file so that only the symbols files of the installed modules or the dependencies of the test suites are included in the zip file. Test: m droid dist && inspect the entries included in the symbols.zip file Bug: 395989947 Change-Id: Icd55ed1bd76b688829f302daebbd1cc32356fe30
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.