commit | eac89fa9cb329bc3bb2bcb8ce5fbcc937d2fb9d8 | [log] [tgz] |
---|---|---|
author | Justin Yun <justinyun@google.com> | Wed Jul 31 13:33:59 2019 +0900 |
committer | Justin Yun <justinyun@google.com> | Wed Jul 31 13:34:35 2019 +0900 |
tree | f156409be25179634d593b2c8184854861720108 | |
parent | 76fc1ce5ff514469fe53a9c65976c7edf13dabd6 [diff] | |
parent | 0a81687a251b34a75133e882dc4de9723eaefb87 [diff] |
resolve merge conflicts of 0a81687a251b34a75133e882dc4de9723eaefb87 to qt-r1-dev-plus-aosp Bug: None Test: I solemnly swear I tested this conflict resolution. Change-Id: Iee31e0df5e5d2b94c9ba7d6815fbbb41497c33c6
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.