| commit | a102909e09dd61298d3ee15190105ac4951b4860 | [log] [tgz] |
|---|---|---|
| author | Mårten Kongstad <amhk@google.com> | Mon May 08 11:51:59 2023 +0200 |
| committer | Mårten Kongstad <amhk@google.com> | Tue May 09 15:27:42 2023 +0200 |
| tree | 6fdbd1c177927fa8af7fc17c76625bfef092ae8a | |
| parent | 872023376e67a3b9b858095dc1a5d071895b9e79 [diff] |
aconfig: add dump protobuf format Introduce a new protobuf format to represent the all flags parsed by aconfig. This data in this new format is similar to that of the internal cache object, but the protobuf is a public API for other tools to consume and any changes to the proto spec must be backwards compatible. When aconfig has matured more, Cache can potentially be rewritten to work with proto structs directly, removing some of the hand-written wrapper structs and the logic to convert to and from the proto structs. At this point, the intermediate json format can be replaced by the protobuf dump. Also, teach `aconfig dump` to accept an --out <file> argument (default: stdout). Also, teach `aconfig dump` to read more than once cache file. Note: the new protobuf fields refer to existing fields. It would make sense to split the .proto file in one for input and one for output formats, and import the common messages, but the Android build system and cargo will need different import paths. Keep the definitions in the same file to circumvent this problem. Bug: 279485059 Test: atest aconfig.test Change-Id: I55ee4a52c0fb3369d91d61406867ae03a15805c3
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.