Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / 998ec8fa3470209b8f9045752a460cf6c894539e
commit998ec8fa3470209b8f9045752a460cf6c894539e[log] [tgz]
authorRamy Medhat <abdelaal@google.com>Wed Sep 02 09:56:50 2020 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Wed Sep 02 09:56:50 2020 +0000
treea224026f8bcdc82ebae080df9234e0ad995d73f3
parent8707038bffbe7fee4325515d16892d9176455a3c [diff]
parent428006cf4dc171fd25c774f592a1455a81cf45a8 [diff]
[automerger skipped] [DO NOT MERGE] Add RBE mk file to support bootstrapping RBE and setting relevant am: 7298be1b47 am: edd7e730e3 -s ours am: 428006cf4d -s ours

am skip reason: Change-Id Ifb6bfd9f7292346f4750a6a409aa0def4e3c0363 with SHA-1 ec8b8dfa3e is in history

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

Change-Id: I8fbf4b398486f432d88031e5a7834c9528d86ac0
tree: a224026f8bcdc82ebae080df9234e0ad995d73f3
  1. common/
  2. core/
  3. packaging/
  4. target/
  5. tests/
  6. tools/
  7. .gitignore
  8. buildspec.mk.default
  9. Changes.md
  10. CleanSpec.mk
  11. Deprecation.md
  12. envsetup.sh
  13. help.sh
  14. navbar.md
  15. OWNERS
  16. rbesetup.sh
  17. README.md
  18. tapasHelp.sh
  19. 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.