| commit | 828828ba07f871aec5ba19c71714367016a023dd | [log] [tgz] |
|---|---|---|
| author | Petri Gynther <pgynther@google.com> | Thu Mar 04 11:04:03 2021 -0800 |
| committer | Petri Gynther <pgynther@google.com> | Fri Mar 05 17:45:03 2021 -0800 |
| tree | 3810fdf71025d20b964ac6c1199fd0ca1637f94d | |
| parent | b579ef2cf9854bf17e6936bc9675d295429cba66 [diff] |
Add support for building vendor_ramdisk.img Allow BoardConfig.mk to set: BOARD_BUILD_VENDOR_RAMDISK_IMAGE := true to build: out/target/product/<name>/vendor_ramdisk.img This is done to support GKI device kernel development. Kernel developers build vmlinux + DTB + GKI kernel modules locally and then use kernel build tools to output: * vmlinux + ramdisk.img => boot.img * GKI kernel modules + DTB + vendor_ramdisk.img => vendor_boot.img In other words, kernel developers use ramdisk.img and vendor_ramdisk.img as prebuilts for building flashable boot.img and vendor_boot.img directly from the kernel development environment. Test: make vendorramdisk with BOARD_BUILD_VENDOR_RAMDISK_IMAGE := true Test: make vendorramdisk with BOARD_BUILD_VENDOR_RAMDISK_IMAGE omitted Change-Id: Id67839887b6bf608f4a5f13384c551c12ee9fdbd
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.