bb520729e8
Fill in aconfig.proto. Define Aconfig definitions (for introducing flags and setting their values) and Overrides (for overriding flags regardless of what their definitions say). More changes to the proto schema are expected when more of the aconfig project is outlined. Use proto2 instead of proto3: this will cause the protobuf text parser to error on missing fields instead of returning a default value which is ambiguous, especially for booleans. (Also, the text protobuf parser doesn't provide good error messages: if the input is missing a field, the error is always "1:1: Message not initialized"). Unfortunately the generated Rust wrappers around the proto structs land in an external crate, which prevents aconfig from adding new impl blocks. Circumvent this by converting the data read from proto into structs defined in the aconfig crate. Change main.rs to parse (static) text proto. Also add dependency on anyhow. Bug: 279485059 Test: atest aconfig.test Change-Id: I512e3b61ef20e2f55b7699a178d466d2a9a89eac |
||
---|---|---|
common | ||
core | ||
packaging | ||
target | ||
tests | ||
tools | ||
.gitignore | ||
banchanHelp.sh | ||
buildspec.mk.default | ||
Changes.md | ||
CleanSpec.mk | ||
Deprecation.md | ||
envsetup.sh | ||
help.sh | ||
METADATA | ||
navbar.md | ||
OWNERS | ||
PREUPLOAD.cfg | ||
rbesetup.sh | ||
README.md | ||
shell_utils.sh | ||
tapasHelp.sh | ||
Usage.txt |
Android Make Build System
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.