| commit | 3d51ac07efc8039872263c5fd226b5caa023b359 | [log] [tgz] |
|---|---|---|
| author | nelsonli <nelsonli@google.com> | Wed Jul 24 16:25:05 2019 +0800 |
| committer | nelsonli <nelsonli@google.com> | Wed Jul 31 10:10:29 2019 +0800 |
| tree | f4299e7e2ac0dcab000e5d433dbf85dcdc372e16 | |
| parent | 5f42d56a2444ece68053867f2bfb136e19d246b5 [diff] |
VTS: Create vts-core suite and packaging rules
For migrating most existing VTS test to executable by Base TradeFed, we have to
create vts-core suite and test all of the modules in vts-core first.
And add the packaging rules for vts-core suite.
Bug: 137921421
Test: (1) add test_suites: ["vts-core"], to any module or patch aosp/1089570
(2) $ m vts-core
(3) check this module in the vts-core.zip
Change-Id: I7a52b3ee400f58e6c383638396ced7194d6bc65d
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.