| commit | f02734e91586e59048189de3288a1df79b96c2a9 | [log] [tgz] |
|---|---|---|
| author | Mårten Kongstad <amhk@google.com> | Fri Jun 02 11:34:24 2023 +0200 |
| committer | Mårten Kongstad <amhk@google.com> | Fri Jun 02 16:46:28 2023 +0200 |
| tree | 02ec43527aa055b9343bf9368cc7ca185dbde2b5 | |
| parent | 83a8760bbc62940f6b5913e0e4168ced2fca5869 [diff] |
aconfig: add create-device-config-defaults command DeviceConfig is the backend for READ_WRITE flags. Add a new command "create-device-config-defaults" to create a file that DeviceConfig will read to pre-populate its data store on first init. This will be used to quickly switch flag values during CI tests: rebuilding and reflashing a device would have the same effect, but would be costlier. This feature is not expected to be used outside CI tests. Note: because DeviceConfig only works with READ_WRITE flags, the generated file excludes READ_ONLY flags. Bug: 285468565 Test: atest aconfig.test Change-Id: I4caff1a10647b8da0ce4e3615678993a957a92dd
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.