| commit | 6ec582160b118a85d6752186cff7468052f23bb5 | [log] [tgz] |
|---|---|---|
| author | Cole Faust <colefaust@google.com> | Mon Dec 09 16:16:24 2024 -0800 |
| committer | Cole Faust <colefaust@google.com> | Mon Dec 09 16:16:24 2024 -0800 |
| tree | de789fecca788a3dbbad20cb0625f8189f1cd77a | |
| parent | f65a4a219aa53c88243c973f5c0053fbca9caaed [diff] |
Remove unassigned event log tags feature .logtags files are a mapping of an integer -> name. However, there is an unused feature where you could put a '?' instead of an integer, and then the build system would assign a number to it, taking care to avoid all other already-assigned numbers across the source tree. This feature makes it hard to support some things we're working towards, like incremental soong and treble common system images, so remove it. Also modernize the python scripts a little. Bug: 382515940 Test: m event-log-tags Change-Id: I33550daf66e00683c95c53a5958d59d25b37470a
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.