commit | f02aadfd274f1f0571f76af7d142df9b0271c0e8 | [log] [tgz] |
---|---|---|
author | Zhuoyao Zhang <zhuoyao@google.com> | Mon Jun 10 18:28:25 2024 +0000 |
committer | Zhuoyao Zhang <zhuoyao@google.com> | Mon Jun 10 18:28:25 2024 +0000 |
tree | 1025e8f153c20802b01c768b4b890254c753f3b5 | |
parent | bfcac4a398ad8e625ec0d9c9df1b83d7caf50cef [diff] |
Support tool event logging for fastboot This is part of the adte team's effort to collect metrics that help understand the bottlenecks in the Android local testing workflow. Added a fastboot function in build/envsetup.sh which wraps the actual fastboot binary with the logging script Bug: 346363374 Test: source build/envsetup.sh && lunch aosp_cf_x86_64_phone-trunk_staging-userdebug && fastboot --version tested in both bash and zsh Change-Id: Ia8d29b4323b64f9f853ee096728993096d7babe9
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.