commit | 7b11b7106a05319b5234231911737db65e34ad82 | [log] [tgz] |
---|---|---|
author | Zhuoyao Zhang <zhuoyao@google.com> | Wed Apr 24 22:58:20 2024 +0000 |
committer | Zhuoyao Zhang <zhuoyao@google.com> | Sat Apr 27 01:01:50 2024 +0000 |
tree | 9b5e88f3f7cd30ebf912803b573d43408c4bd736 | |
parent | c6e4a86b0391830ccc2ee6e81be2482a2dc6e659 [diff] |
Add a Clearcut tool event logger Implement a binary that logs tool events to Clearcut. The binary is designed to be eventually called by the `run_tool_with_logging` script in the `envsetup.sh` script that sets up the build environment. Only start and stop events are currently logged for each invocation. Test: atest tool_event_logger_test bug: 331638854 Change-Id: I9268e4cb986975ceda171204e6ce8ef1732eaeea
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.