Google Git
Sign in
android / platform / build / 6cbe894cc2d0b4f934f21fe68f4cf003df87739b
commit6cbe894cc2d0b4f934f21fe68f4cf003df87739b[log] [tgz]
authorandroid-build-team Robot <[email protected]>Wed May 29 07:33:39 2019 +0000
committerandroid-build-team Robot <[email protected]>Wed May 29 07:33:41 2019 +0000
tree00b64f68833e34c6f61e89f64472ba646b9f6acc
parenta3916b9fe928844e36deea0b59f033d716d7bca7 [diff]
Version bump to PQ3B.190705.002 [core/build_id.mk]

Change-Id: I2cc99bd9d1959e1cb7c8bdf9c71bdb30c736ac0c
1 file changed
tree: 00b64f68833e34c6f61e89f64472ba646b9f6acc
  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.