commit | 29376de44c95431e8e85f393cc7bdc7fbd80d14b | [log] [tgz] |
---|---|---|
author | Zhi Dou <zhidou@google.com> | Mon Mar 10 14:20:58 2025 +0000 |
committer | Zhi Dou <zhidou@google.com> | Mon Mar 10 17:13:28 2025 +0000 |
tree | bfd02565faa726bb6b2e40f532f78e3315cb3d3f | |
parent | fdca9c65fb8ff6c10067467d986624965f09cb04 [diff] |
add tool exported-flag-check This tool ensures that exported flags are used as intended. Exported flags, marked with `is_exported: true` in their declaration, are designed to control access to specific API features. This tool identifies and reports any exported flags that are not currently associated with an API feature, preventing unnecessary flag proliferation and maintaining a clear API design. This tool should be triggered by the build system when it builds all_aconfig_declarations Test: atest exported-flag-check Bug: 336800305 Change-Id: Ia1574cb05478eb2f329b959ee69ad13a4abdad50
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.