Explicitly include installer tools in recovery media ramdisk

The recovery media runtime depends on these, we will make these
injectable down the line for other Android product usages.

Bug: 467740614, 467740616
Test: m pack-recovery-image
Cherrypick-From: https://googleplex-android-review.googlesource.com/q/commit:d3ce9e4c9c2083ab3f95f0f404536cbd772bf8c2
Merged-In: Ia4e4d0f67f3e2b2bfedce6c5f58ecf5e53b441be
Change-Id: Ia4e4d0f67f3e2b2bfedce6c5f58ecf5e53b441be
1 file changed
tree: d8c5abad4a7070eb6d20f6330c478459c3511117
  1. backported_fixes/
  2. ci/
  3. common/
  4. core/
  5. packaging/
  6. target/
  7. teams/
  8. tests/
  9. tools/
  10. .gitignore
  11. Android.bp
  12. banchanHelp.sh
  13. buildspec.mk.default
  14. Changes.md
  15. CleanSpec.mk
  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.