| commit | d067588a26fc3fe4de51ddb00b750824ed266429 | [log] [tgz] |
|---|---|---|
| author | Zhuoyao Zhang <zhuoyao@google.com> | Fri Jun 21 20:47:57 2024 +0000 |
| committer | Zhuoyao Zhang <zhuoyao@google.com> | Fri Jun 21 21:03:03 2024 +0000 |
| tree | dad6ab3a3e30c8418974550d856ff2a34ca33898 | |
| parent | 79d04e41154a3abf272251af6fc9814c40ebd556 [diff] |
Support uploading host_name info in the tool event logger host_name info is useful in several use cases including 1) to distinguish the concurrent tool invocations from the same user. 2) to understand the potential different performance from different hosts (e.g. local workstation VS cloudtop). 3) required to integrate the tool event log with the EPR system. Test: atest tool_event_logger_test Bug: 348482213 Change-Id: I98422b3f8ccec73d57fcdcdedac91780c448dc47
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.