| commit | 12c7751ff229f1648d7cdb5c0e07dd0c8008a788 | [log] [tgz] |
|---|---|---|
| author | Nelson Li <nelsonli@google.com> | Thu Jul 11 14:24:34 2024 +0800 |
| committer | Nelson Li <nelsonli@google.com> | Wed Jul 17 12:02:59 2024 +0800 |
| tree | 712f5b7426b0ebab68235d4ddf8c372591486fb2 | |
| parent | 3a2d9d2c50d19b54ac1b8b054a1864f3b05ea401 [diff] |
Add BOARD_MOVE_GSI_AVB_KEYS_TO_VENDOR_BOOT as a soong config variable This variable allow customizing whether the `ramdisk` and `vendor_ramdisk` are included in the boot image (ramdisk) or the vendor boot image (vendor_ramdisk). This is useful for devices that move recovery resources to the vendor boot partition Bug: 347636127 Test: Add it to soong_config_module_type Change-Id: If7a126fe8bdc69173921c0b01f85fb9480f4a36f
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.