commit | bdef28f2ee5a75acda723698b5306100f731b69b | [log] [tgz] |
---|---|---|
author | Ramji Jiyani <ramjiyani@google.com> | Mon Jan 24 04:15:19 2022 +0000 |
committer | Ramji Jiyani <ramjiyani@google.com> | Mon Jan 24 21:27:52 2022 +0000 |
tree | 2bba037eed0f4074b980872e42ed116e91a222dc | |
parent | 034e777339a8cd702e1f81775a5fc78b950df2e9 [diff] |
releasetools: system_dlkm: add image to dist zip Bug: 200082547 Test: Manual builds: 1. Set BOARD_USES_SYSTEM_DLKM_PARTITION 2. Set BOARD_PREBUILT_SYSTEM_DLKM_IMAGE to external image - Check that "m dist" put the system_dlkm image in out/dist/aosp_cf_x86_64_phone-img-eng.ramjiyani.zip Signed-off-by: Ramji Jiyani <ramjiyani@google.com> Change-Id: I8b7dd40e178db7fe542253bff19040095847fa57
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.