| commit | 0a1dd239ccc30170a071c9330040c15e694ba458 | [log] [tgz] |
|---|---|---|
| author | Kelvin Zhang <zhangkelvin@google.com> | Fri Aug 18 11:02:19 2023 -0700 |
| committer | Kelvin Zhang <zhangkelvin@google.com> | Fri Aug 18 11:02:19 2023 -0700 |
| tree | e2fa1b6f70f10db3c10075d8c2ceb3a20f30c886 | |
| parent | 8f830007321ef0cbabd5f581da5a6429843ff399 [diff] |
Move 16K kernel modules to /lib/modules/`uname -r`_16k Store 16K kernel modules in separate directory. This allows us to store both 4k and 16k kernel modules in vendor_boot and have init load from the right path. Test: th Bug: 293313353 Change-Id: I55cd33404defc71dfbd350517d2aa51bebdb3d06
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.