| commit | b4ef8e92aa92e23022c2f01e04de149cfebd350a | [log] [tgz] |
|---|---|---|
| author | Dan Shi <dshi@google.com> | Sat Mar 28 13:25:21 2020 -0700 |
| committer | Dan Shi <dshi@google.com> | Fri Apr 03 11:21:15 2020 -0700 |
| tree | 5be30878d7d840e8b35a92b9eed82e67d5e47794 | |
| parent | 60e8ff4d0d2a884e2d43e199fe6835d4c033f6d9 [diff] |
Cleanup VTS-Core and VTS10 related artifacts Bug: 151896491 Test: none Change-Id: I5a42dcbe34866751a54f059d363f1866bff7d47a Merged-In: I5a42dcbe34866751a54f059d363f1866bff7d47a (cherry picked from commit c5e98d405fc0c8ae377be3530f33b14c41f5c569)
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.