Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 683c493cc792800465706c1512b7f99183298706
commit683c493cc792800465706c1512b7f99183298706[log] [tgz]
authorPeter Collingbourne <pcc@google.com>Wed Jul 06 15:49:20 2022 -0700
committerPeter Collingbourne <pcc@google.com>Wed Jul 06 15:57:26 2022 -0700
treee14386a4b44f9548e203be5ef62cd379932c9be7
parent294aeed6d517b0a758ebf00cb73d77b565f52e49 [diff]
Allow building super.img on targets without BOARD_BUILD_SUPER_IMAGE_BY_DEFAULT set.

With this change, if BOARD_BUILD_SUPER_IMAGE_BY_DEFAULT is unset, a
target will be declared for super.img so it becomes possible to build it
(e.g. with `m superimage`), but it will not be part of the default `droid`
target. This is useful for building a `super.img` on targets that do
not normally need one without needing to go through a slow `m dist` step.

Change-Id: I599e93b3fc41fc2c0642761fcda757c40e2736d6
1 file changed
tree: e14386a4b44f9548e203be5ef62cd379932c9be7
  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.