| commit | a5bec26ceb0211efe701c40efc54340531b5d815 | [log] [tgz] |
|---|---|---|
| author | Zhuoyao Zhang <zhuoyao@google.com> | Tue Nov 05 19:28:23 2024 +0000 |
| committer | Zhuoyao Zhang <zhuoyao@google.com> | Tue Nov 05 19:37:36 2024 +0000 |
| tree | 20d0a92520686731a5aa9b102374c6959dc96263 | |
| parent | fe4906450c784d6ab9ee13a048f52f9a0cee4940 [diff] |
Rollout edit monitor to 10% users Simplified the logic in whether to enable edit monitor by passing the rollout percentage directly instead of reading from a env variable as now we do not rely on any env var to control the rollout precentage. Test: atest edit_monitor_utils_test Bug: 365617369 Change-Id: Ia04d5737dafe2c9715a02f84eb5d75ba6119ceb4
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.