Gitiles
Code Review Sign In
review.shift-gmbh.com / SHIFTPHONES / android_build / 4b2306b41c1d6da406dc75a41acda2c02f9b3371
commit4b2306b41c1d6da406dc75a41acda2c02f9b3371[log] [tgz]
authorTao Bao <tbao@google.com>Fri Jan 11 12:28:09 2019 -0800
committerTao Bao <tbao@google.com>Fri Jan 11 12:28:09 2019 -0800
tree8cd71e797cabf0346d508dd68673d204f535f26e
parent2e77d4ee2c0f8f8a7fa815823b6563bbe37670db [diff]
releasetools: Update OWNERS.

Test: N/A
Change-Id: I0c6ac3cd04cc6034787d4b8b90fbd61349c54655
1 file changed
tree: 8cd71e797cabf0346d508dd68673d204f535f26e
  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.