commit | f4017412e2617bf25d8a961cc953e99ed8e83b5b | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Fri Sep 24 15:47:44 2021 -0700 |
committer | Colin Cross <ccross@android.com> | Fri Sep 24 16:58:03 2021 -0700 |
tree | e42232b4ad60fe48d914fab48c4a00606bdfb4f3 | |
parent | b9306ac477d4d2be5cfd079f56b583bb0009e687 [diff] |
Support per-testcase directories in all test suites There are cases where two modules try to install the same test data into CTS, which results in collisions when CTS puts the data for all tests in the same directory. Add a flag that allows enabling a per-testcase directory for an individual test for all test suites. Bug: 193168159 Test: cts-tradefed run commandAndExit CtsBionicTestCases Change-Id: I4bfaaedfe0e6b8df9c75125b3e2762a4f0d5b395
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.