| commit | ec657cedbb84e26540a0e062915bc53b6cb0caaf | [log] [tgz] |
|---|---|---|
| author | Zhuoyao Zhang <zhuoyao@google.com> | Fri Dec 06 19:17:46 2024 +0000 |
| committer | Zhuoyao Zhang <zhuoyao@google.com> | Fri Dec 06 22:53:35 2024 +0000 |
| tree | de7e0fabf03c7c1f8b95d56c272a458148d258e0 | |
| parent | 96c15d81dd4b4f59e4e982733801ee95abc9d224 [diff] |
Synchronize the setup process of edit monitor This cl ensures only one edit monitor instance is in the setup proecess by requesting exclusive file lock on a setup lock file. If there is already an edit monitor in setup process, other instances trying to setup will fail. This prevents race conditions when multiple edit monitor instance are starting. Test: atest daemon_manager_test bug: 382135550 Change-Id: Ia8bd2f35318ae81fc002ccce62e2fde3b8cae26b
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.