commit | e0c7f7682358965ea8666434a18a3bc1b9bd987a | [log] [tgz] |
---|---|---|
author | Simran Basi <sbasi@google.com> | Fri Dec 08 17:07:06 2017 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Fri Dec 08 17:07:06 2017 +0000 |
tree | a3194867d3e9de9b71dc1420d48042dfff48221b | |
parent | 0025fee6a04d406bd71459b74ebd177453d08a65 [diff] | |
parent | 15949b76abbac9245340ccdaf0ee00393194884d [diff] |
Add support for multiple LOCAL_COMPATIBILITY_SUITES & undefined testcase directories. am: 0dd1fb9112 am: a749d6bdb5 am: 5a8f82d4a1 am: 7b26faa5ea am: acaa4cc623 -s ours am: 203a1f407b -s ours am: f1be8db559 -s ours am: fd5769448d -s ours am: 15949b76ab -s ours Change-Id: If79b90b216e5697ed70a0db8ccd879c5c5884021
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.