Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 49b70b67ce491c2bcdd65e5b17c3b4cb3c2d640e
commit49b70b67ce491c2bcdd65e5b17c3b4cb3c2d640e[log] [tgz]
authorRamji Jiyani <ramjiyani@google.com>Thu Dec 01 00:55:10 2022 +0000
committerRamji Jiyani <ramjiyani@google.com>Thu Dec 01 00:55:10 2022 +0000
tree68c80d777b9cc8e992499d3705cace136359622e
parenta4dc4a3ac7b286a5b37fb18c82939e7cd6ee0cd1 [diff]
system_dlkm: Remove manual module copy

Rather than copying GKI modules from source folder
pointed by BOARD_SYSTEM_DLKM_SRC; use core build
macro BOARD_SYSTEM_KERNEL_MODULES as list
of GKI modules to be copied on the system_dlkm partition.

This leverages core infrastructre already present for
the kernel modules for vendor_dlkm, odm_dlkm, etc.

Bug: 232430739
Test: TH
Change-Id: Ic53f450eb426dc4ec38fc80b7ceaa625c8ab206b
Signed-off-by: Ramji Jiyani <ramjiyani@google.com>
1 file changed
tree: 68c80d777b9cc8e992499d3705cace136359622e
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. banchanHelp.sh
  9. buildspec.mk.default
  10. Changes.md
  11. CleanSpec.mk
  12. Deprecation.md
  13. envsetup.sh
  14. finalize-aidl-vndk-sdk-resources.sh
  15. finalize-cleanup.sh
  16. finalize-step-1-for-build-target.sh
  17. finalize-step-1.sh
  18. finalize_branch_for_release.sh
  19. help.sh
  20. METADATA
  21. navbar.md
  22. OWNERS
  23. PREUPLOAD.cfg
  24. rbesetup.sh
  25. README.md
  26. tapasHelp.sh
  27. Usage.txt
README.md

Android Make Build System

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.