Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / fa40c04cba0522bfc781f4e8e15673f9ccff097a
commitfa40c04cba0522bfc781f4e8e15673f9ccff097a[log] [tgz]
authorKelvin Zhang <zhangkelvin@google.com>Wed Nov 09 10:59:25 2022 -0800
committerKelvin Zhang <zhangkelvin@google.com>Wed Nov 09 14:43:17 2022 -0800
treebc373ce45ca5621f100915e332e31aaf9a568da5
parenta56bce6ef1f41c906c7f65a725a8accaf05b87a3 [diff]
Fix recovery OTA error on merged targets

Currently, when merging target files, system side's update_engine
version info is copied into the merged target_files. This causes
recovery OTA failure, because update_engine_sideload daemon in recovery
is from vendor side. To fix it, use the older version of update_engine
config when merging target files.

Test: th
Bug: 257426678
Change-Id: I5d3304366749995c99a61ca0645a22ee047f1465
3 files changed
tree: bc373ce45ca5621f100915e332e31aaf9a568da5
  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.sh
  17. finalize_branch_for_release.sh
  18. help.sh
  19. METADATA
  20. navbar.md
  21. OWNERS
  22. PREUPLOAD.cfg
  23. rbesetup.sh
  24. README.md
  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.