Gitiles
Code Review Sign In
gerrit.omnirom.org / android_build / b3795b7933990b7cec975a3f9049454a5762527a
commitb3795b7933990b7cec975a3f9049454a5762527a[log] [tgz]
authorJaeMan Park <jaeman@google.com>Wed Aug 14 14:11:15 2024 +0900
committerJaeMan Park <jaeman@google.com>Wed Aug 14 14:11:15 2024 +0900
tree2dc510eb242ebda3c69b1938a7033ce14fef658f
parent5ab8f4a84b03513323d6c12b7dd16e4899b22b61 [diff]
Fix build error while creating CHD image

While building CHD image, it failed with the error

KeyError: 'system_dlkm_base_fs_file'

Fix the build error by deleting proper props in the python code.

Bug: 359578756
Test: Building CHD image using build_cf_hybrid_device.py should not failed
Change-Id: Iae84ff080b8f6bf3b8d22b26865ea3e74815ac37
1 file changed
tree: 2dc510eb242ebda3c69b1938a7033ce14fef658f
  1. ci/
  2. common/
  3. core/
  4. packaging/
  5. target/
  6. teams/
  7. tests/
  8. tools/
  9. .gitignore
  10. Android.bp
  11. banchanHelp.sh
  12. buildspec.mk.default
  13. Changes.md
  14. CleanSpec.mk
  15. cogsetup.sh
  16. Deprecation.md
  17. envsetup.sh
  18. help.sh
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  25. tapasHelp.sh
  26. 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.