f3c2823040
am: e93b598eb8
am: ae2159dbcf
-s ours
am skip reason: Change-Id Icc52500cfc0a555e11d1a467b2da0649c7f5d31f with SHA-1 e23fd86f1b
is in history
Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/11789975
Change-Id: I8e2dbb0adc95339ab04074ee559c152bb6b36ea4
1d1bb3b94f
am: 27d4463cf5
am: 02dcbdb3f9
am: 373f5fad03
am: 0c5aef4d5b
581e1f4f1f
am: 821ecd2b56
am: 0336f08679
am: 2dcaca7c3a
am: 570df23fac
4e0bce688c
am: 09dd92a862
am: 8e8444d4fe
am: f609e203c4
am: 345cd28fbb
5d0a024d7b
am: 479c9c549b
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.