commit | 0597a9d7757e3753a1508981d2310e9ac92c3c43 | [log] [tgz] |
---|---|---|
author | Zhuoyao Zhang <zhuoyao@google.com> | Fri Oct 04 21:11:18 2024 +0000 |
committer | Zhuoyao Zhang <zhuoyao@google.com> | Wed Oct 23 22:14:34 2024 +0000 |
tree | a64d2108d92f85e60b73df5395c7d5f92c0a74d1 | |
parent | 8a2257965207cf117a33bc52dc9e39c94e35a343 [diff] |
Filter out the logs from inotify_buffer in edit monitor The inotify_buffer logs every filesystem event received (in Debug level) which pollutes the edit monitor log. This cl filters out the logs from inotify_buffer.py to keep the log clean. Test: make edit_monitor and test it locally Bug: 365617369 Change-Id: Ib7951c2fd7d8cabf3f56a2cd0364c26f682ca977
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.