|tagger||Jinseong Jeon <firstname.lastname@example.org>||Thu Jan 24 01:06:00 2019 -0800|
|author||Søren Gjesse <email@example.com>||Wed Jan 23 13:38:49 2019 +0100|
|committer||Søren Gjesse <firstname.lastname@example.org>||Wed Jan 23 12:41:28 2019 +0000|
Version 1.4.29 Cherry-pick: Fix not setting offset on DexItemBasedConstString replacement CL: https://r8-review.googlesource.com/c/r8/+/33145 Cherry-pick: Add test for gms core with forced jumbo string rewriting CL: https://r8-review.googlesource.com/c/r8/+/33228 Cherry-pick: Don't generate compat rules when tracing reflective use CL: https://r8-review.googlesource.com/c/r8/+/32845 Cherry-pick: Mark fields accessed by reflection as both read and written CL: https://r8-review.googlesource.com/c/r8/+/33271 Cherry-pick: Print proper reason for kept-by-reflection edges. CL: https://r8-review.googlesource.com/c/r8/+/33263 Cherry-pick: Ensure that we can merge desugared java8 classes CL: https://r8-review.googlesource.com/c/r8/+/33281 Cherry-pick: Add support for -libraryjars in ProguardTestBuilder. CL: https://r8-review.googlesource.com/c/r8/+/33274 Cherry-pick: Throw for unimplemented APIs in ProguardTestBuilder CL: https://r8-review.googlesource.com/c/r8/+/33262 Cherry-pick: Guard check-cast elimination when in-value is null constant CL: https://r8-review.googlesource.com/c/r8/+/33300 Cherry-pick: Revert "Revert "Assert that definitionFor is only called on non-null class types."" CL: https://r8-review.googlesource.com/c/r8/+/33280 Bug: 123152027 Bug: 123242448 Bug: 123215165 Bug: 69590587 Bug: 123164442 Bug: 123269162 Change-Id: I06db0b137ceb3d3410f04680c5bbecc697b8f905
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
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:
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
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
Typical steps to run tests:
$ tools/test.py --no_internal
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.
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 email@example.com.