commit | f0add55066f76e62fc1781f4c2b9ea8fd8ede269 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Thu Oct 31 19:13:50 2019 -0700 |
committer | Colin Cross <ccross@android.com> | Fri Nov 01 13:34:46 2019 -0700 |
tree | 0c391a7135867a023dad6c4eb7d90ffa8c2416ec | |
parent | 15e75e8807c81980e8d9e2a87332643a9662d541 [diff] |
Use system modules for turbine in Make turbine supports taking system modules on the command line, now that we target Java language level 1.9 and use system modules by default switch turbine to match javac. This is equivalent to Ieee07502151da0d5693bb8929213d495c039106b in Soong. Test: m java Change-Id: Ib91c6f57b316f48f1ab819e4e1d2dc2e0ee42988
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.