| commit | 7f22db8fc1fcff100e6916d4e7b09149c8b6b6b1 | [log] [tgz] |
|---|---|---|
| author | Zhuoyao Zhang <zhuoyao@google.com> | Thu Oct 17 17:40:34 2024 +0000 |
| committer | Zhuoyao Zhang <zhuoyao@google.com> | Thu Oct 24 16:36:10 2024 +0000 |
| tree | fd4cb20a9cd67e11d2a2f2bfb6cc2f40f2cf54d5 | |
| parent | ba64f31b5698b3c7440f1b6f4df1bfb202a208b0 [diff] |
Support --dry_run option in edit monitor If --dry_run option is set, edit monitor runs without actually sending the edit logs to clearcut Test: atest edit_monitor_test bug: 365617369 Change-Id: I793d9b0a2e16ffa70fe03d1d3f53d676a1d86cf3
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.