commit | 6bcc93983b684d45752a2340bd5b20d8e99fcf80 | [log] [tgz] |
---|---|---|
author | Nicolas Geoffray <ngeoffray@google.com> | Tue Jan 22 21:25:04 2019 +0000 |
committer | Nicolas Geoffray <ngeoffray@google.com> | Thu Jan 24 13:10:22 2019 +0000 |
tree | d286e289550e3e7110662a64126577be458bd960 | |
parent | ba3e26d5da097fcec495200c96fade9ee1147ede [diff] |
Differentiate between runtime apex jars and framework jars. And use the apex paths of runtime apex jars. Test: m Change-Id: I7bd6e6029c2d5d596d672545271b5ed9819090b6
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.