Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 12542bdd8e11c3f72b1429f46da05b074e1661e7
commit12542bdd8e11c3f72b1429f46da05b074e1661e7[log] [tgz]
authorTom Cherry <tomcherry@google.com>Tue Aug 07 13:12:02 2018 -0700
committerTom Cherry <tomcherry@google.com>Tue Aug 07 13:14:09 2018 -0700
tree1ee77455d5f0b30434ac8d6ee48a73e51e5adca8
parente1feef50251c6df596d712fce5ad9e7bd527c9be [diff]
Add more whitelisted artifacts for the recovery image

Bug: 112318375
Test: build succeeds
Change-Id: I4d12af2b1744a9b79ee8b79f7d15e9b7940d7305
1 file changed
tree: 1ee77455d5f0b30434ac8d6ee48a73e51e5adca8
  1. core/
  2. target/
  3. tests/
  4. tools/
  5. .gitignore
  6. Android.mk
  7. buildspec.mk.default
  8. Changes.md
  9. CleanSpec.mk
  10. envsetup.sh
  11. help.sh
  12. navbar.md
  13. OWNERS
  14. README.md
  15. tapasHelp.sh
  16. 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.