| commit | 79c422a0c2ca9f9682d0b4b96ba3dc7b9c7fc568 | [log] [tgz] |
|---|---|---|
| author | android-build-team Robot <android-build-team-robot@google.com> | Tue Jun 16 07:08:11 2020 +0000 |
| committer | android-build-team Robot <android-build-team-robot@google.com> | Tue Jun 16 07:08:11 2020 +0000 |
| tree | b65a60848b6ec607593b0f713c61448ec9cfa2f9 | |
| parent | d8437068e738e6a0d57535d5ddf65bb62e60e3d6 [diff] | |
| parent | 658b373e324b1d425fc8572c7ef7a8fd59076f7e [diff] |
Snap for 6593884 from 658b373e324b1d425fc8572c7ef7a8fd59076f7e to mainline-release Change-Id: I4b64bdcb75c8d1c364fd35520705f09e8e517e9f
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.