| commit | a95f2b230cbf68b5b373c649ce11b8c2f231b97d | [log] [tgz] |
|---|---|---|
| author | Jihoon Kang <jihoonkang@google.com> | Wed Dec 06 00:46:01 2023 +0000 |
| committer | Jihoon Kang <jihoonkang@google.com> | Thu Dec 07 22:36:59 2023 +0000 |
| tree | 30789e3696c730f2809829e904108d11e78c0959 | |
| parent | 2118e738b2683e9dc0654464e3e2808e8f06543d [diff] |
Add new dump format map in aconfig The `aconfig dump --format map` lists aconfig keys mapped to its boolean values that represents whether the flag is enabled or not, as seen below: ``` flag.name1=true flag.name2=false ``` Test: aconfig dump --format map --cache out/soong/.intermediates/build/make/tools/aconfig/aconfig.test.flags/intermediate.pb && inspect output Bug: 306024510 Change-Id: Ic4990c168f6fa9c87869113ba695c07394adbc67
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.