| commit | 294111393ecbcc9d15ad15a74fa31a66946b9409 | [log] [tgz] |
|---|---|---|
| author | Tobias Thierer <tobiast@google.com> | Fri Nov 17 14:06:51 2017 +0000 |
| committer | Tobias Thierer <tobiast@google.com> | Thu Jan 04 11:08:14 2018 +0000 |
| tree | 140c6eca0c13d8660812b5385696b17a6431fd82 | |
| parent | a52691b12afa2e7e42ca009808326fde3df07098 [diff] |
Build with OpenJDK 9 -target 1.8 by default (attempt 4). This is cherry-picked from attempt 3, which was reverted due to http://b/70862583. Before this CL topic, the build toolchain for .java source files used OpenJDK 8, targeting 1.8 (v52 class files) by default. This CL topic switches the default to OpenJDK 9, but still targeting 1.8 (v52 class files) by default. If USE_ERROR_PRONE is set to true, then the default remains OpenJDK 8. Code in the Android platform should generally be unaffected, but if host tools that are now compiled and run using OpenJDK 9 are causing problems for your team, then let me know. To manually switch back to the old behavior for now (continue using OpenJDK 8), run this command in your shell: export EXPERIMENTAL_USE_OPENJDK9=false Bug: 69449021 Test: Treehugger Test: art/test/testrunner/run_build_test_target.py -j40 art-interpreter Test: dalvik/dx/tests/run-all-tests (cherry picked from commit ab1e54d5f1389314de49ca5aa3003e33b9d4aba7) Change-Id: I119be15bd95747722114b970400b740fa47bf9e0 Merged-in: Ic42a518c90515b497e5cecec444ded373e403a4b
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.