| commit | 0b9d289e2a8fe6262421e9a5483558c2023679dd | [log] [tgz] |
|---|---|---|
| author | Oriol Prieto Gasco <opg@google.com> | Mon Nov 20 16:23:51 2023 +0000 |
| committer | Oriol Prieto Gasco <opg@google.com> | Mon Nov 20 21:30:18 2023 +0000 |
| tree | 4ae295c744f98a186eb9b33a3720d3529a15db1d | |
| parent | 8faa4a588001cad91b98a7577373745752a29971 [diff] |
Add is_exported field to aconfig.proto When a flag is exported, it can be read by code built in other containers. By default flags are not exported. Set this to true if your flag is gating a public API which may be called from other containers (typically, a flag used in @FlaggedAPI annotations). Test: atest aconfig.test Bug: 311152500 Change-Id: I53e3ed18b96c1518f04172d5933ef96b41ccda7e
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.