| commit | 04735a8ef239248756e310c2fa841f77a0cdf636 | [log] [tgz] |
|---|---|---|
| author | TreeHugger Robot <treehugger-gerrit@google.com> | Thu Apr 23 23:20:16 2020 +0000 |
| committer | Android (Google) Code Review <android-gerrit@google.com> | Thu Apr 23 23:20:16 2020 +0000 |
| tree | bb0fe473745656045efae1c4b2b26d88190031dc | |
| parent | c0f3be1309f9522a508e8faf3b64d0aa91b26ce8 [diff] | |
| parent | 4b6b2003a97ac30bc918a36d0720a7f7d5c63846 [diff] |
Merge changes I465ea6c9,I57b77d7c,I536a286d,Ie16a7bf7 into rvc-dev * changes: generate multiple boot.img files in aosp_arm64 create emulator_arm64 device for sdk_phone_arm64 to use support multiple boot.img files in release tools multi boot.img support cleanups
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.