| commit | 9801d9b7b24ef8e371e8ebfcc784a3b6f3791191 | [log] [tgz] |
|---|---|---|
| author | Dan Shi <dshi@google.com> | Mon Feb 26 23:26:06 2018 +0000 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Feb 26 23:26:06 2018 +0000 |
| tree | 14f825f918a86fc56518b48ff31dea7dca9b7b78 | |
| parent | 47db251db085f7e33df68bcc1dbcce5d2693329a [diff] | |
| parent | 6dbd9e3df92ef2372e2f6ae15741880b907860d1 [diff] |
Merge "Default test to AndroidJUnitTest for auto-generated test config." am: ce1fa25d1b am: d91129eea9 am: 6dbd9e3df9 Change-Id: I84ee22fa20b08fb3db27d5e5d0e03f097a11463f
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.