| commit | ad5321a48a274de63e89fe2d290398591dd85381 | [log] [tgz] |
|---|---|---|
| author | Mathieu Chartier <mathieuc@google.com> | Wed Jan 17 21:40:36 2018 +0000 |
| committer | android-build-merger <android-build-merger@google.com> | Wed Jan 17 21:40:36 2018 +0000 |
| tree | 4d6e31c5562b2958c0ab20359f929a069761fa22 | |
| parent | 7215d15542232dbb98b6d1e4d549ad8409e65c17 [diff] | |
| parent | a4f424f6525b2c499dbc305157675fac10047d37 [diff] |
Merge changes Iba0c3893,Icf3039ef am: dc9f2de809 am: 0f6b16580c am: a4f424f652 -s ours Change-Id: I6ccfa31c31e756ef4c31a19124f0ca83e8b8f10e
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.