| commit | 4515a88302790b0e012ce9995cea5b0a75c70b01 | [log] [tgz] |
|---|---|---|
| author | Dan Shi <dshi@google.com> | Wed Apr 01 04:47:05 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Apr 01 04:47:05 2020 +0000 |
| tree | b4fe8c9073d915f503649b929dd7bd7bbfc244ea | |
| parent | 125765fa79452f8b7725806f66c6b18a984a8f80 [diff] | |
| parent | 60e8ff4d0d2a884e2d43e199fe6835d4c033f6d9 [diff] |
Merge "Rename VTS to VTS10" am: 916be61b91 am: ed51dee98e am: 474ebdd3e9 am: 371d7b5194 am: 60e8ff4d0d Change-Id: I51c830e4f1035db5f68a039066e59c9967bc1f3f
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.