Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 6d75a854efcef67d5b3f9e33e4d1ea3ff119d512
commit6d75a854efcef67d5b3f9e33e4d1ea3ff119d512[log] [tgz]
authorOleg Lyovin <ovlevin@sberdevices.ru>Wed Mar 22 17:50:02 2023 +0300
committerOleg Lyovin <ovlevin@sberdevices.ru>Wed Mar 22 17:53:26 2023 +0300
tree77b5965f0db7de5928feab01b8f220c346057ccb
parent0a25e6740462a4b88b6b90cfb838591329b158d2 [diff]
Fix choosing wrong diff tool for recovery-from-boot patch

'bsdiff' tool should be used when recovery and boot image
have mismatching entries. This includes not only the case
when system_as_root enabled, but include_recovery_dtbo and
include_recovery_acpio too.

Add check if they are enabled to synchronize logic with
core/Makefile, which already takes this into account.

Test: make dist -j
Change-Id: Ie673403ae8eae446d006cc524dd48ac6c56194fc
Signed-off-by: Oleg Lyovin <ovlevin@sberdevices.ru>
1 file changed
tree: 77b5965f0db7de5928feab01b8f220c346057ccb
  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. help.sh
  15. METADATA
  16. navbar.md
  17. OWNERS
  18. PREUPLOAD.cfg
  19. rbesetup.sh
  20. README.md
  21. shell_utils.sh
  22. tapasHelp.sh
  23. 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.