Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / fbf53522cf0d27d4f3771e4e03b840f0d0da21b1
commitfbf53522cf0d27d4f3771e4e03b840f0d0da21b1[log] [tgz]
authorAidan Wolter <awolter@google.com>Fri Mar 17 20:17:35 2023 +0000
committerAidan Wolter <awolter@google.com>Fri Mar 17 20:17:35 2023 +0000
tree0735f9a065251e74c8477d4af3c201e3dfa5dfba
parent4e7daf65467299e3b26631e5a71ed28434982c50 [diff]
[config] Boards can supply custom super image script

Some boards may need to customize the format of the super image. We will
now provide the variable BOARD_CUSTOM_BUILD_SUPER_IMAGE so that boards
can provide their own script for constructing the super image. This
mimics similar code in the same file for allowing boards to supply a
custom VBMeta (BOARD_CUSTOM_AVBTOOL) or boot image
(BOARD_CUSTOM_MKBOOTIMG).

Bug: None
Change-Id: I461caeb6dfb705fd5c671228fc35561ed403a1cb
1 file changed
tree: 0735f9a065251e74c8477d4af3c201e3dfa5dfba
  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-locally-mainline-sdk.sh
  17. finalize-sdk-rel.sh
  18. finalize-step-1-for-build-target.sh
  19. finalize-step-1.sh
  20. finalize-step-2-for-build-target.sh
  21. finalize-step-2.sh
  22. finalize_branch_for_release.sh
  23. help.sh
  24. METADATA
  25. navbar.md
  26. OWNERS
  27. PREUPLOAD.cfg
  28. rbesetup.sh
  29. README.md
  30. shell_utils.sh
  31. tapasHelp.sh
  32. 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.