| commit | b66b11ec9a4e53f3e933616d7f6b3335bfdec8f2 | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Mon Dec 05 13:04:42 2022 -0800 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Mon Dec 05 13:04:42 2022 -0800 |
| tree | c412c2d9903a13a885af975b3ca8aea1f69b76f7 | |
| parent | 33544af4d14576c9f758203ace5e4e9350684a28 [diff] |
Allow empty modules.load file to be generated Currently, if BOARD_*_KERNEL_MODULES_LOAD is set to empty string, we default to load all modules listed in BOARD_*_KERNEL_MODULES. For system_dlkm, we do not want to load any modules unless they are dependency of vendor kernel modules. Therefore we need to create an empty modules.load file for system_dlkm. Add 'false' as an out of band value to indicate that an empty modules.load file should be generated. Bug: 149866755 Test: th Change-Id: Ieaaeb2f9a824e97671acff465bbd4da83dfd9aa0
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.