| commit | 02b6cdf5e35b2713e7c9df23fd483d66db37198c | [log] [tgz] |
|---|---|---|
| author | Liz Kammer <eakammer@google.com> | Tue Nov 10 10:32:27 2020 -0800 |
| committer | Liz Kammer <eakammer@google.com> | Wed Nov 11 14:10:45 2020 -0800 |
| tree | 0b902423954af3dac8179b0c47490b81cef6692e | |
| parent | 6f83343e7eae8fd826770009cabe1827754152f7 [diff] |
Update mts task to make mts-${MODULE} test suites
In addition to a single mts test suite, we want to have slim, per-module
mts test suites. This introduces the infrastructure to build a test
suite for each module added to mts_modules.
Bug: 170318013
Test: m mts
Test: m mts-tzdata
Change-Id: Ib93ea14e6fa99e362785681cd7660a1ca37e0fe3
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.