commit | 77c9f0c9cb784fa6e4c1a254a0f83eeb5694cd61 | [log] [tgz] |
---|---|---|
author | Zhi Dou <zhidou@google.com> | Wed Oct 11 19:49:56 2023 +0000 |
committer | Zhi Dou <zhidou@google.com> | Fri Oct 20 21:04:00 2023 +0000 |
tree | 76f73e98d28ada16797fe16c8dbffa36b4900467 | |
parent | d1aa0735ee1b5857ce5fe9054bb798f6441e8295 [diff] |
add script to help override flag value locally Add a script to help to create flag value building rules. The script will only extract necessary information from the value file but it will not validate the file. The validation will defer to building system. For input ``` flag_value { package: "com.android.aconfig.test" name: "disabled_ro" state: DISABLED permission: READ_ONLY } flag_value { package: "com.android.demoapp.test" name: "enabled_ro" state: DISABLED permission: READ_WRITE } flag_value { package: "com.android.aconfig.test" name: "enabled_rw" state: ENABLED permission: READ_WRITE } ``` The output Android.bp file will be like ``` VALUE_LIST_LIST = [ aconfig-local-com.android.demoapp.test, aconfig-local-com.android.aconfig.test ] aconfig_values { name: "aconfig-local-com.android.demoapp.test", package: "com.android.demoapp.test", srcs: [ "override_values.textproto", ] } aconfig_values { name: "aconfig-local-com.android.aconfig.test", package: "com.android.aconfig.test", srcs: [ "override_values.textproto", ] } ``` Bug: 298692416 Test: source build/envsetup.sh && overrideflags, and then check the output Change-Id: Ife4063e079811e0b29046be7a6bc127cad668ed0
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.