| commit | d28da5cfe3e9362f2c83241e106505703f9f4d73 | [log] [tgz] |
|---|---|---|
| author | Zhuoyao Zhang <zhuoyao@google.com> | Tue Sep 24 19:46:12 2024 +0000 |
| committer | Zhuoyao Zhang <zhuoyao@google.com> | Tue Oct 01 18:22:36 2024 +0000 |
| tree | a579455dff11e3f0c1919401311029ab081be10c | |
| parent | ae332aea96352698a8323b74c15a56891521d949 [diff] |
Support to cleanup all existing edit monitor instances Add a cleanup method in daemon manager to stop all the existing edit monitor instances and place a block sign to provent any edit monitor to start. This method is only used in emergency case when something goes wrong with edit monitor and need immediate cleanup to prevent damage to the system. Test: atest daemon_manager_test bug: 365617369 Change-Id: I8bff4f82a8ce272ccafb4ff8b076f05f56609426
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.