commit | 6c7e02e74e047bbbb9901c8d86e45cd638abc87f | [log] [tgz] |
---|---|---|
author | Yi-Yo Chiang <yochiang@google.com> | Sun Apr 04 21:30:48 2021 +0800 |
committer | Yo Chiang <yochiang@google.com> | Sun Apr 04 14:25:47 2021 +0000 |
tree | a52e6649275f874862dd1f696b01b6ac1b7d898a | |
parent | 08b0004c9cb714c6b9a7e8112ded0570253cc92b [diff] |
Support installing modules.options file Usage: ``` BOARD_(VENDOR|VENDOR_RAMDISK)_KERNEL_MODULES_OPTIONS_FILE(_ver) := \ $(wildcard <path of modules.options in source tree>) ``` Then the modules.options would be installed as (vendor_dlkm|vendor_ramdisk)/lib/modules/(ver/)modules.options. Also fix bug where the kernel version subdir is missing when generating modules.blocklists file. Bug: 182417593 Bug: 184238876 Test: Create a options file with incorrect syntax, verify build fails Test: Verify the new macro indeed installs the options file Change-Id: I7ba56e9dd8d73055bc276446c385a8d79080c2a6
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.