commit | 1519d4351ef3f30bb0dec0a0d3f426fa689ececa | [log] [tgz] |
---|---|---|
author | Yi-Yo Chiang <yochiang@google.com> | Sun Apr 04 16:03:10 2021 +0800 |
committer | Yi-Yo Chiang <yochiang@google.com> | Sun Apr 04 20:40:17 2021 +0800 |
tree | 514bde4838fbcb0d49561ba2eb7c49688d74cfc3 | |
parent | 08b0004c9cb714c6b9a7e8112ded0570253cc92b [diff] |
Refactor vendor_boot v4 build logic and add more checks Add more checks around BOARD_BOOT_HEADER_VERSION in board_config.mk. Refactor generation logic of vendor_boot ramdisk fragments. Consolidate initialization and validation check to its own section. Adjust some variable names and initialization sequence so the follow-up change can land more cleanly. Rename variable name "dir" so that it don't collide with the Makefile function "$(dir ...)". Bug: 183395459 Test: Presubmit; Change should be no-op with respect to build artifacts. Test: Modify BoardConfig of CF and m dist. Verify the vendor_boot.img with unpack_bootimg. Change-Id: I8785c40dd9f87f3797a56ada93e65939d27d0e9b
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.