f61420f4c1
am: 596cbaabd3
am: c9e6fc3439
am: b19e7c527b
am: 94101e9adb
am: 5d6e7f7d6e
am: c064cceaa6
am: f21f19b490
-s ours
am skip reason: Merged-In Iefbd1fff39d557fa352a53662d70bc734a255564 with SHA-1 f61420f4c1
is already in history
Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/27779597
Change-Id: I0b3830c4e796495c538718328d95f5209cbc7584
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
f61420f4c1
am: 596cbaabd3
am: c9e6fc3439
am: b19e7c527b
am: 94101e9adb
am: 5d6e7f7d6e
am: f6f39f6d6d
025ca884e7
am: cd6f4aa267
am: e7380612e4
am: dfa6ac7cfc
am: c7f7581d2a
am: 5053ab2397
am: 2d9122055b
am: 5f53ed3950
Android Make Build System
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.