Google Git
Sign in
android / platform / build / 8b316d4870
commit8b316d487048ecc30bb253716d8e4dcca365e7fc[log] [tgz]
authorandroid-build-team Robot <android-build-team-robot@google.com>Wed Aug 19 02:22:02 2020 +0000
committerandroid-build-team Robot <android-build-team-robot@google.com>Wed Aug 19 02:22:05 2020 +0000
tree13d0060e019e047a3472bfcb6787b1353215c3f6
parent4e7b3d526ae2ff0129744bde91c49e32f79cfc53 [diff]
Version bump to RP1A.201005.002 [core/build_id.mk]

Change-Id: I6ad01ccb62f30d41bd08a7096f985bc9aac1c814
1 file changed
tree: 13d0060e019e047a3472bfcb6787b1353215c3f6
  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.