| commit | 980052abf63b59f9dfb6f7601c1f80949d244a56 | [log] [tgz] |
|---|---|---|
| author | Jim Shargo <jshargo@google.com> | Mon Aug 07 21:09:20 2023 +0000 |
| committer | Jim Shargo <jshargo@google.com> | Tue Aug 08 16:57:42 2023 +0000 |
| tree | 5565f0c7fc3894829ffee41334a128aa5abf90f7 | |
| parent | 1afb7ffec29d9edcaf9ef565c84a390a6142fed0 [diff] |
Clean up after ourselves in the Rust Benchmark Template There's a compliance check for tradefed that ensures that configs for tests are set to cleanup after themselves. See: https://cs.android.com/android/platform/superproject/main/+/main:tools/tradefederation/core/javatests/com/android/tradefed/presubmit/GeneralTestsConfigValidation.java;l=425-429;drc=1fb7fe35bf7c843b5bac510476d63e4c8b436a48 This causes new benchmarks to fail presubmits. Test: CLs with rust benchmarks pass presubmits now Change-Id: I14f64ee3343bcf9bd2d77f547dc16b9c15bf4082
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.