commit | 5fffb0ac6f26418428cac2c7ac80165db0fe9938 | [log] [tgz] |
---|---|---|
author | Ian Zerny <zerny@google.com> | Mon Feb 11 13:54:22 2019 +0100 |
committer | Ian Zerny <zerny@google.com> | Mon Feb 11 13:54:22 2019 +0100 |
tree | 18fbeec9707bf6d7ee64d78a4fc4edf193a8cf9a | |
parent | f719ca4ef354eb19f53f80722836b13b16496b0b [diff] |
Add a pinned JDK 9 to third_party and update Gradle to 5.2 This CL makes various changes to update our build to JDK 9 and Gradle 5.2. The build will by default use third_party/{gradle/gradle, openjdk/openjdk-9.0.4} to build. This is done by directly using third_party/gradle/gradle and reading the location of the JDK from tools/jdk.py. That value is then set as JAVA_HOME for the subprocess in tools/gradle.py and picked up by the running tests via Syste.getProperty("java.home"). To override the JDK to use, both tools/gradle.py and tools/test.py take a --java-home argument which is used to define -Dorg.gradle.java.home which will take precedence over JAVA_HOME in gradle. FYI, the build.gradle is configured to issue a warning if the current Java Home differes from the expected pinned version, but will not change it. The summary of changes needed to update are: - Add tools/jdk.py which is the canonical place to update the current default JDK. - Add --java-home flag for running with a non-pinned JDK (eg, JDK 8) to gradle.py. - Add various max-heap-size settings to control heap size (for example, running JDK 8 requires manually increasing size of the gradle instance for compilation). - Update the inner-classes tests which are no longer considered malformed on JDK 9. - Update path to classes build dir (changed in gradle 4+). Change-Id: I28789c0eaacb865b31b46e8daec0da8e62bb24a3
The R8 repo contains two tools:
D8 is a replacement for the DX dexer and R8 is a replacement for the Proguard shrinking and minification tool.
The R8 project uses depot_tools
from the chromium project to manage dependencies. Install depot_tools
and add it to your path before proceeding.
The R8 project uses Java 8 language features and requires a Java 8 compiler and runtime system.
Typical steps to download and build:
$ git clone https://r8.googlesource.com/r8 $ cd r8 $ tools/gradle.py d8 r8
The tools/gradle.py
script will bootstrap using depot_tools to download a version of gradle to use for building on the first run. This will produce two jar files: build/libs/d8.jar
and build/libs/r8.jar
.
The D8 dexer has a simple command-line interface with only a few options.
The most important option is whether to build in debug or release mode. Debug is the default mode and includes debugging information in the resulting dex files. Debugging information contains information about local variables used when debugging dex code. This information is not useful when shipping final Android apps to users and therefore, final builds should use the --release
flag to remove this debugging information to produce smaller dex files.
Typical invocations of D8 to produce dex file(s) in the out directoy:
Debug mode build:
$ java -jar build/libs/d8.jar --output out input.jar
Release mode build:
$ java -jar build/libs/d8.jar --release --output out input.jar
The full set of D8 options can be obtained by running the command line tool with the --help
option.
R8 is a Proguard replacement for whole-program optimization, shrinking and minification. R8 uses the Proguard keep rule format for specifying the entry points for an application.
Typical invocations of R8 to produce optimized dex file(s) in the out directory:
$ java -jar build/libs/r8.jar --release --output out --pg-conf proguard.cfg input.jar
The full set of R8 options can be obtained by running the command line tool with the --help
option.
Typical steps to run tests:
$ tools/test.py --no_internal
The tools/test.py
script will use depot_tools to download a lot of tests and test dependencies on the first run. This includes prebuilt version of the art runtime on which to validate the produced dex code.
In order to contribute to D8/R8 you have to sign the Contributor License Agreement. If your contribution is owned by your employer you need the Corporate Contributor License Agreement.
Once the license agreement is in place, you can upload your patches using ‘git cl’ which is available in depot_tools. Once you have a change that you are happy with you should make sure that it passes all tests and then upload the change to our code review tool using:
$ git cl upload
On your first upload you will be asked to acquire credentials. Follow the instructions given by git cl upload
.
On successful uploads a link to the code review is printed in the output of the upload command. In the code review tool you can assign reviewers and mark the change ready for review. At that point the code review tool will send emails to reviewers.
For questions, reach out to us at r8-dev@googlegroups.com.
For D8, find known issues in the D8 issue tracker or file a new D8 bug report.
For R8, find known issues in the R8 issue tracker or file a new R8 bug report.