| commit | 810a0ba56f1939c2811ff2f1319fa4a41019d502 | [log] [tgz] |
|---|---|---|
| author | Steve Muckle <smuckle@google.com> | Wed Nov 13 13:29:02 2019 -0800 |
| committer | Steve Muckle <smuckle@google.com> | Wed Nov 20 10:46:13 2019 -0800 |
| tree | 8cccf16d60874653fe575a8f508d358c05cb5ffa | |
| parent | 83131cbef9df90b4647d6f3f6ec18132e810f0bd [diff] |
add BOARD_*_KERNEL_MODULE_ARCHIVE support
It may be the case that the list of kernel modules to be copied into
various partitions is not known at the time the build is invoked. To
support this configuration, create a set of make variables, each of
which can be set to the path of a zip archive of kernel modules to be
used.
Bug: 144317186
Bug: 144844424
Test: build and verify *.ko in vendor, repackage prebuilt
kernel modules into zip, build and verify *.ko in vendor
Change-Id: Ie6f7e2c72efa11d39be341920dd46e4ed6678fe1
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.