| commit | f4686696c4bac73cec83c33a8d73aa855bcdd26b | [log] [tgz] |
|---|---|---|
| author | Colin Cross <ccross@android.com> | Mon Oct 01 19:38:25 2018 -0700 |
| committer | android-build-merger <android-build-merger@google.com> | Mon Oct 01 19:38:25 2018 -0700 |
| tree | db8640d1d8ca7a2a9e14614167aa75ce012cd63d | |
| parent | 74da73fd999cd2c675fafc657dd2f1f279b25d6c [diff] | |
| parent | 1033e0516b83b53d110b03c8d22cb67243c20917 [diff] |
Merge changes I9e73c0b8,Iac5c4327,Idf6fbc94 am: 7307de5e0c am: 4aa10a3cc5 am: 1033e0516b Change-Id: I208a549fc8dd99fb511327a1c9c4d07e4f6cf54b
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.