commit | 098029302ebec19202a90298e703ba0566e49bf5 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Wed Aug 07 14:03:18 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Wed Aug 07 14:03:18 2019 -0700 |
tree | cdf665d6d6d8c14a53d43334d8115b3d11be1c39 | |
parent | 0e8a871805340778b25c216a6e4cf217d7659a54 [diff] | |
parent | 0271e7ece00c68bc6d6859d47e6519c1086a0def [diff] |
Merge "Move make_recovery_path and sparse_img to modules." am: 4c9527b314 am: f882684d85 am: 3b357afb65 am: f1c2cb2b75 am: 0271e7ece0 Change-Id: I3e57e8c5886268bb8aea2fe2b9372f55b47e9fbd
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.