[automerger skipped] Support chained init_boot partition signing am: 425f7d1cb3 am: 296ad0f194 -s ours

am skip reason: Merged-In I65fc7913089ae318d90df55a533d3e2ebd93b029 with SHA-1 acf1b3afe2 is already in history

Original change: https://googleplex-android-review.googlesource.com/c/platform/build/+/20486714

Change-Id: I267d5ad99c9ecc7610d7cc3845bab0faf234ca40
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: 84b23e2c2f28abb1e65bd33a3a5acdebfa2853ea
  1. common/
  2. core/
  3. orchestrator/
  4. packaging/
  5. target/
  6. tests/
  7. tools/
  8. .gitignore
  9. banchanHelp.sh
  10. buildspec.mk.default
  11. Changes.md
  12. CleanSpec.mk
  13. Deprecation.md
  14. envsetup.sh
  15. finalize_branch_for_release.sh
  16. help.sh
  17. METADATA
  18. navbar.md
  19. OWNERS
  20. PREUPLOAD.cfg
  21. rbesetup.sh
  22. README.md
  23. tapasHelp.sh
  24. 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.