| commit | dc2840dafc7d188ee7a4c0fb717fd3d1b2791a99 | [log] [tgz] |
|---|---|---|
| author | Zhuoyao Zhang <zhuoyao@google.com> | Thu Sep 19 23:29:27 2024 +0000 |
| committer | Zhuoyao Zhang <zhuoyao@google.com> | Wed Sep 25 19:05:34 2024 +0000 |
| tree | 3ee7df6681ced3ef3ad4e62f5554c69cc44e009c | |
| parent | 480c30410ca67f0ef65216163fe5419e3e29e49e [diff] |
Support monitoring the subprocess in edit monitor The daemon manager will keep monitoring the memory/cpu usage of the daemon process and kill it in case the process is consuming too much resources (specified with a threshold). Test: atest daemon_manager_test bug: 365617369 Change-Id: Ic9f8eb5a338de4e9cf7c8aba381ad752cf6aeba0
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.