| commit | 1065523a5e668c22601bf5f4608d4ff8d64e9ec3 | [log] [tgz] |
|---|---|---|
| author | Ramji Jiyani <ramjiyani@google.com> | Thu Jan 20 06:43:09 2022 +0000 |
| committer | Ramji Jiyani <ramjiyani@google.com> | Fri Jan 21 21:39:15 2022 +0000 |
| tree | 6dcbb4942158bc089406e5caab1755376c9e7379 | |
| parent | 95ec3b899e2493a4872e23306715f9a7f1ab89cc [diff] |
Add support to build system_dlkm.img There are 2 choices to build system_dlkm.img for the system_dlkm partition for Android T launch devices and must choose one. 1. Use kernel prebuilt system_dlkm.img - BOARD_PREBUILT_SYSTEM_DLKM_IMAGE to point image 2. Build from kernel prebuilt system_dlkm_staging - PRODUCT_BUILD_SYSTEM_DLKM_IMAGE Both requires: BOARD_SYSTEM_DLKM_PARTITION_SIZE and must be 64MB or higher in size (enforced via vts). Bug: 200082547 Test: TH Test: atest vts_system_dlkm_partition_test Signed-off-by: Ramji Jiyani <ramjiyani@google.com> Change-Id: I83435123bd8aa3d04ab8a8b650a95fbab0bc49f2
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.