| commit | 1b8636bd7d2d0acc3b1af8b7db8e43e900de0f99 | [log] [tgz] |
|---|---|---|
| author | Mårten Kongstad <amhk@google.com> | Thu Jun 22 10:12:24 2023 +0200 |
| committer | Mårten Kongstad <amhk@google.com> | Thu Jun 22 16:50:33 2023 +0200 |
| tree | 6a112302ec9a5547869df6e4bd33177094c1986b | |
| parent | 0e5e1749bbff84c06831943daefbf44a7531333a [diff] |
aconfig: add proto `bug` field Add a `bug` field on the flag_declaration and parsed_flag proto messages. This field is optional in the sense that it can occur zero or more times, and aconfig will simply pass any value through. Bug fields are included in the aconfig dump format, which can be processed by other tools. Also unify how protos.rs checks that fields marked 'optional' in the proto file, but in practice are 'required', are actually set. Test: atest aconfig.test aconfig.test.java Bug: 288261336 Change-Id: I93de0005674822c6ff4d699bdc2c6509763a7f7f
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.