| commit | 190304985c87c718861186169bf508105501b99c | [log] [tgz] |
|---|---|---|
| author | Dennis Shen <dzshen@google.com> | Wed Mar 06 17:33:01 2024 +0000 |
| committer | Dennis Shen <dzshen@google.com> | Wed Mar 06 17:46:18 2024 +0000 |
| tree | e6504f7821ee362ad554f9a11d30e52bfb1ca0db | |
| parent | cdde8f39f84a73ab1f3dfa9af5e9934d3651bad1 [diff] |
aconfig: create aconfig_storage_file binary to print the storage files To help debug storage files. We need a binary to parse the storage binary files and print out the flag values like device_config list command. In addition, aconfig_storage_file needs to provide a public api to allow flag cli to call to get the flag values. Therefore creating this change. This change includes the following changes: 1, Implement debug print trait for package table, flag table, and flag value struct. So the debug dump is more readable. 2, Add a list flag api to create a vector of flag name and value tuples given the storage file names. This api will be used by aconfig_storage_file binary as well as aconfig flag cli. 3, Add a main.rs to create aconfig_storage_file binary to debug print storage files or list all the flags in storage files. It has two subcommands. 3.1 print command: aconfig_storage_file print --file <storage file> --type <package_map|flag_map|flag_val> This command produce a debug print of a single the storage file content 3.2 list command: aconfig_storage_file list --package_map <package map file> --flag_map <flag map file> --flag_val <flag value file> This command parses all storage files to print out list of flag values in the following form: <package>/<flag>, <value> ... <package>/<flag>, <value> Bug: b/321077378 Test: manual test of the binary command Change-Id: I000e216d13854f853cbd9b63cabb6db3a47dbece
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.