Google Git
Sign in
android / platform / build / 5d198edc1b25a87192aec136bff3d13f02438bef
commit5d198edc1b25a87192aec136bff3d13f02438bef[log] [tgz]
authorandroid-build-team Robot <[email protected]>Fri Apr 10 07:37:04 2020 +0000
committerandroid-build-team Robot <[email protected]>Fri Apr 10 07:37:06 2020 +0000
tree9f9ee1e2b7479288898a794a688ca047ac30605f
parentbd9c28121c123a9c8e67f1253722cd37e33e097d [diff]
Version bump to QD4A.200317.017 [core/build_id.mk]

Change-Id: I9dac6e353c0d8f65953583b46c4371879df19f0a
1 file changed
tree: 9f9ee1e2b7479288898a794a688ca047ac30605f
  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. envsetup.sh
  12. help.sh
  13. navbar.md
  14. OWNERS
  15. README.md
  16. tapasHelp.sh
  17. 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.