commit | 88fc2bdd195b29e8ea976f317773724ec06473d7 | [log] [tgz] |
---|---|---|
author | Bowgo Tsai <bowgotsai@google.com> | Wed Jan 05 20:19:25 2022 +0800 |
committer | Bowgo Tsai <bowgotsai@google.com> | Thu Jan 06 17:50:04 2022 +0800 |
tree | 3aab369297f4ec234aa88410e7f0c9a80ff2a62e | |
parent | 8beddf2e7e047bf47fd12d1c51563d84613f680b [diff] |
Avoid packing ramdisk into GKI boot-*.img If init_boot.img is present, the GKI boot-*.img should not include the ramdisk because the ramdisk will be packed into the init_boot.img instead. The "has_ramdisk" flag incorrectly checks the condition of: prebuilt_name != "boot.img" to see if it is a boot.img. Because "has_ramdisk" was added before we packed multiple GKI boot-*.img, e.g., boot-5.10.img, boot-5.10-lz4.img, etc., into the target files. Fix this by checking the partition_name is "boot" or not. Also moving the logic into a new function with comments for each condition. Bug: 203698939 Bug: 213028932 Test: sign_target_files_apks \ --gki_signing_key=external/avb/test/data/testkey_rsa4096.pem \ --gki_signing_algorithm=SHA256_RSA4096 \ ./out/dist/*-target_files-eng.*.zip signed.zip, then unpack_bootimg to checks the signed boot-*.img has no ramdisk Change-Id: I5354669feb54d547dbe797e51b1b1baa187cb7cf
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.