| commit | 5e0ff33d0f8d4d4da269b4f2cf4395ffcaca1f7b | [log] [tgz] |
|---|---|---|
| author | Steve Muckle <smuckle@google.com> | Thu Feb 20 10:19:06 2020 -0800 |
| committer | Steve Muckle <smuckle@google.com> | Thu Feb 20 10:19:06 2020 -0800 |
| tree | db0d350141b23c837829bff468b6adc86b32c412 | |
| parent | 24e2f7c0f1cb6521041cebe7625794c25c8ab71f [diff] |
do not clear output kernel module directory When using an archive to provide kernel modules, the archive is directly expanded into the output directory. The output directory is currently removed prior to that to ensure no stale modules are present if they were removed as part of a change in an incremental build. Unfortunately if kernel modules are also provided via the regular BOARD_*_KERNEL_MODULES macros, the removal of the output kernel module directory will race with the copying of kernel modules in BOARD_*_KERNEL_MODULES, resulting in some of those kernel modules not being present in the output. Kernel modules removed from BOARD_*_KERNEL_MODULES do not currently get removed from the output directory in an incremental build anyway. So in order to support using BOARD_*_KERNEL_MODULES and BOARD_*_KERNEL_MODULES_ARCHIVE conurrently, take out the removal of the output directory prior to archive expansion. Bug: 149866863 Change-Id: Ib373650ddcb0fb5782a13d68a8869a9117e42ccc
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.