commit | c116988ed1568e6ed3dbae92c3d881b60d7d2548 | [log] [tgz] |
---|---|---|
author | Dan Willemsen <dwillemsen@google.com> | Fri Jan 18 17:11:00 2019 -0800 |
committer | android-build-merger <android-build-merger@google.com> | Fri Jan 18 17:11:00 2019 -0800 |
tree | d78b1fc588314a4a1a01f508408409fccdc01cbb | |
parent | 03e61a74a85536b5eb0586f9d32e406b2448a540 [diff] | |
parent | b20ba12b8090ae1dafb38eef28050ccc79c88c42 [diff] |
Merge changes I685ab841,I6ab7e488 am: 215e2c828c am: b20ba12b80 Change-Id: I93f44c548c1406f0e5e7021cdd533eb7c849964c
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.