Google Git
Sign in
android / platform / build / 80d2e87132
commit80d2e871327d2b14632d7264e9c49283ae44bc0f[log] [tgz]
authorandroid-build-team Robot <android-build-team-robot@google.com>Thu May 20 06:35:23 2021 +0000
committerandroid-build-team Robot <android-build-team-robot@google.com>Thu May 20 06:35:25 2021 +0000
tree15e52f6d7dcfc938c90a008c6c78f1a1917ac013
parent86eb166b191c46d4ff8320199b0a65b27947a71b [diff]
Version bump to RD2A.210605.007 [core/build_id.mk]

Change-Id: Ib8bf01b66b4d8871e488a1a5fa06773954a6feb2
1 file changed
tree: 15e52f6d7dcfc938c90a008c6c78f1a1917ac013
  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.