| commit | 46d758bd49c7b3fc9b56df6c4a540187a475b7be | [log] [tgz] |
|---|---|---|
| author | Ted Bauer <tedbauer@google.com> | Tue Mar 12 19:28:58 2024 +0000 |
| committer | Ted Bauer <tedbauer@google.com> | Wed Mar 13 14:46:31 2024 +0000 |
| tree | 320f77c013d4395e21ef41833bee9bbd6e1751ac | |
| parent | bf29fffff37e7273165f9be2648965612b12d918 [diff] |
aflags: show staged values for each flag. Lines now have a new column, and look like this: com.android.example.flag1 enabled - server read-write system com.android.example.flag2 enabled (->disabled) server read-write system The dash represents no change on boot, the (->value) represents a change to value on the next boot. Test: adb shell device_config put staged multitasking*com.android.wm.shell.enable_taskbar_navbar_unification true && adb shell aflags list | grep navbar_unification Bug: 324436145 Change-Id: I022460bc69fcb2ccd9c6db8f060fcbd0337d1ea6
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.