| commit | d435d23f42decbed9e583ed109b1ba12b7ec328e | [log] [tgz] |
|---|---|---|
| author | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jan 22 23:09:23 2020 +0000 |
| committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Wed Jan 22 23:09:23 2020 +0000 |
| tree | 64c76a379cf36e4032b319a0ca4336e9865be2f8 | |
| parent | ee7c5f38b9e5281e5e17cb53dde561e962f05933 [diff] | |
| parent | f243891f3f21f814d08e6d37ebc3686e7da5a573 [diff] |
Merge "Do not check VINTF if no files" am: 84c1309730 am: f243891f3f Change-Id: I705ec6fe12412bd44289ab0bcb73d6aade83d1ac
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.