Gitiles
Code Review Sign In
review.blissroms.org / platform_build_make / b6056d68561a4e97226c7a708b8285f71c99bbd1
commitb6056d68561a4e97226c7a708b8285f71c99bbd1[log] [tgz]
authorVictor Chang <vichang@google.com>Tue Aug 06 16:54:08 2019 +0100
committerVictor Chang <vichang@google.com>Tue Aug 06 16:54:08 2019 +0100
treeccabe543734f2d5abecb2597553545dfcb52125d
parent46d95f752b14aa00527568f56d47b9a4dc72a58d [diff]
Add new core-icu4j after separating icu4j from core-libart

Bug: 138994281
Test: m droid
Change-Id: Ib2a7a464a4cc0030061c018c1941db5c28a90b7d
2 files changed
tree: ccabe543734f2d5abecb2597553545dfcb52125d
  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. README.md
  17. tapasHelp.sh
  18. 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.