commit | a380533f135fb7925ef8ef4fac3c87634cb75b4c | [log] [tgz] |
---|---|---|
author | Dennis Song <denniscy@google.com> | Fri Aug 04 07:08:17 2023 +0000 |
committer | Dennis Song <denniscy@google.com> | Fri Aug 04 07:08:17 2023 +0000 |
tree | fb43eec59735faaf58216400e763348a7a78c56c | |
parent | 196c70bf23829dd691d8ad0978bbd911a53fe207 [diff] |
Remove system_dlkm from _FRAMEWORK_PARTITIONS system_dlkm partition is related to GKI, so it should be in the same category as boot image. Test: merge_target_files \ --path otatools \ --framework-target-files framework-target_files.zip \ --vendor-target-files vendor-target_files.zip \ --output-target-files merged-target_files.zip Bug: 294482075 Change-Id: Ie8f60d72f44d31e1bc3b556735b92ed0a2fda662
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.