| commit | fd49a0edd8eb730d27c8415be33f9925482e91fb | [log] [tgz] |
|---|---|---|
| author | android-build-team Robot <android-build-team-robot@google.com> | Fri Jun 05 07:25:27 2020 +0000 |
| committer | android-build-team Robot <android-build-team-robot@google.com> | Fri Jun 05 07:25:27 2020 +0000 |
| tree | 6ca0bc7ac0380077666a49102c12d568061c428b | |
| parent | 6364c6c62023e3a4ba2ef25ff06810ae563f20a7 [diff] | |
| parent | d4620668af0a5fb97da525d55fb900023f305542 [diff] |
Snap for 6561534 from d4620668af0a5fb97da525d55fb900023f305542 to mainline-release Change-Id: Ia2cf8862485a8fd78bfca6516fba947d8b0defb9
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.