| commit | 85578e0a9d72efff71f7466251c8cd25024ed494 | [log] [tgz] |
|---|---|---|
| author | Bowgo Tsai <bowgotsai@google.com> | Tue Apr 19 10:50:59 2022 +0800 |
| committer | Bowgo Tsai <bowgotsai@google.com> | Tue Apr 19 17:57:51 2022 +0800 |
| tree | 8991012384c8212aa182737edd7085c032ed1c7f | |
| parent | a9aa002d3b21f248e09c954a36054c5726f40fcd [diff] |
Adding BOARD_BUILD_GKI_BOOT_IMAGE_WITHOUT_RAMDISK GKI targets, e.g., `gki_arm64` or `gki_x86_64` have only boot-*.img files without a ramdisk. It has no other images, e.g., init_boot.img, system.img, etc. The current build system assumes that the ramdisk is either in a boot.img or in a init_boot.img, which is not true for those GKI targets. Adding a new flag to support building boot-*.img without a ramdisk while not building an init_boot.img. Bug: 220834917 Test: build and `unpack_bootimg` Change-Id: I789343c3e3d9ff0c36c0e19680a9792bd31a1c9f
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.