commit | f6ce461f1f7d0f63014252613754cbba5e3d4def | [log] [tgz] |
---|---|---|
author | Steve Muckle <smuckle@google.com> | Thu May 28 18:39:38 2020 -0700 |
committer | Steve Muckle <smuckle@google.com> | Wed Jun 03 11:18:10 2020 -0700 |
tree | 72d57db33d87d26f2a7146b1e40571e3309f469c | |
parent | 7576d5e131f0bc810e7bb0054488f8f4a895b95d [diff] |
refactor kernel module build, add version support Refactor the build support for kernel modules. This refactoring is leveraged to add support for directories of kernel modules in each partition. To add a directory of kernel modules, define BOARD_KERNEL_MODULE_DIRS to include the directory name, for example: BOARD_KERNEL_MODULE_DIRS := 5.4 The build will then check all the usual kernel module related macros with an extension of _5.4, for example you can define BOARD_VENDOR_KERNEL_MODULES_5.4 := <modules to copy> BOARD_VENDOR_KERNEL_MODULES_ARCHIVE_5.4 = <path to archive file> BOARD_VENDOR_KERNEL_MODULES_LOAD_5.4 := <modules for load list> Bug: 157645635 Change-Id: I1687d0ec85c1dcf21350350623b4689aba3f6717 Merged-In: I1687d0ec85c1dcf21350350623b4689aba3f6717
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.