commit | f0e0bff54e1368490a5cc7508f3c7a444227f774 | [log] [tgz] |
---|---|---|
author | Juan Yescas <jyescas@google.com> | Fri Feb 07 14:40:25 2025 -0800 |
committer | Juan Yescas <jyescas@google.com> | Wed Feb 19 12:59:15 2025 -0800 |
tree | 44bda5d753c6f7b653e50bf9dbcf5da03c4f4363 | |
parent | 334dfb7ec574e5127391846983852e0b2ee21828 [diff] |
build: core: Add 16kb modules loaded in Second Stage to vendor_dlkm This change will add the 16kb modules that are loaded in Second Boot Stage to the vendor_dlkm partition. The 16kb modules will be in the directory: /vendor_dlkm/lib/modules/16k-mode This directory will only be available when the 16kb developer option is enabled. Bug: 382569981 Test: Built and booted husky in 4k/16k modes Flag: EXEMPT bug_fix Merged-In: Iaa3a0117184307da7de43cb7dd185b5f457c7bba Change-Id: Iaa3a0117184307da7de43cb7dd185b5f457c7bba
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.