| commit | 9693a5fde80bd34b30099503ef0d6d14e0ad88b3 | [log] [tgz] |
|---|---|---|
| author | Jooyung Han <jooyung@google.com> | Fri Feb 14 13:30:59 2025 +0900 |
| committer | Jooyung Han <jooyung@google.com> | Fri Feb 14 14:01:37 2025 +0900 |
| tree | 41221dc221e8e314b672bc18ce09715bc7dfaa7e | |
| parent | e3dee679310af4c568d3ccedc3948cde639e3dbc [diff] |
vendorkernelramdisk references input list This fixes the incremental build issue that it fails to rebuild even when the input list has changed. BOARD_VENDOR_KERNEL_RAMDISK_KERNEL_MODULES_BLOCKLIST_FILE := /path/to/file Adding the line above triggers rebuilding vendor_kernel_ramdisk.img, which has a new blocklist file. But, removing the line should trigger rebuilding vendor_kernel_ramdisk.img as well, but for now it's not the case because the command for building the image doesn't reference the input files. In this change, the build rule references the input list (not verbatim, but it's enough to reference just the number of input files), so that even when the input list is reduced, the build rule is triggered. Bug: 396542128 Test: see above Change-Id: If37eaeef64b2d2b90c121ce6fb04e1fa00253d5c
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.