c40c0e4cec
am: 4f91b596f8
am: 11e57867e0
am: 0769dc1dd3
am: 9350344f59
am: fc62caefdd
am: fe58bd40e9
am: 19927c34f6
am: 27191fa5ab
Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/29355247 Change-Id: I9111bebd43f27dc7a80e59439d17f23c5eb4742c Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
c40c0e4cec
am: 4f91b596f8
am: 11e57867e0
am: 0769dc1dd3
am: 9350344f59
am: fc62caefdd
am: fe58bd40e9
am: 19927c34f6
am: 27191fa5ab
5c1187e22f
am: 697c44e7dd
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.