| commit | bae5f72a3f8f4811c077bb4d87b21480c392f02e | [log] [tgz] |
|---|---|---|
| author | Zhuoyao Zhang <zhuoyao@google.com> | Fri Sep 20 16:53:59 2024 +0000 |
| committer | Zhuoyao Zhang <zhuoyao@google.com> | Mon Oct 21 21:19:18 2024 +0000 |
| tree | 45f4aa2d819b38f00c9fe4c97bd15988be477bdb | |
| parent | 4a1b00e0e3d273285ebe2e4f6b1f355b7db47a18 [diff] |
Add the basic edit monitor logic The edit monitor uses the watchdog lib to montior any file changes (create, modify, move, delete) under a specific directory, create a edit log based on the file change event and send the edit log to Sawmill through clearcut. Test: Atest edit_monitor_test Bug: 365617369 Change-Id: Ib6e04a43e4dd78ca58c7ccdef56fb4f6bda6e7a5
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.