| commit | c68c6b9530c1a96d94ba12e7d86da62c691b2a92 | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Tue Nov 14 10:54:50 2023 -0800 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Tue Nov 14 12:41:56 2023 -0800 |
| tree | 57a29126c36ca390fe40e43037a30ee945712c39 | |
| parent | c7bc53999d2ade96c5cc0917bd4b3faa12512bff [diff] |
Allow ParseOptions to compose multiple option parsers easily There are certain options which we need to share in multiple binaries, for example, the signer options. Current options parsing function only accepts 1 extra option handler, which is inflexible. Extend it to take a list of extra option handlers. Currently, to add a new CLI flag, caller must append the flag name to `extra_long_opts`, then pass an extra option handler which can handle that option. Define a new dataclass which contains both the CLI flag name and the code to handle that flag for better composition. Test: th Bug: 293313353 Change-Id: I758db66dfd95934f5b2701454d97bfe7d37dc16d
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.