|tagger||Morten Krogh-Jespersen <email@example.com>||Fri Oct 25 12:48:10 2019 +0200|
|author||Morten Krogh-Jespersen <firstname.lastname@example.org>||Fri Oct 25 12:46:15 2019 +0200|
|committer||Morten Krogh-Jespersen <email@example.com>||Fri Oct 25 12:46:15 2019 +0200|
Version 1.6.41 Cherry pick: Add test asserting no renaming of interface clinits using applymapping CL: https://r8-review.googlesource.com/c/r8/+/44541 Cherry pick: Reserve clinits in proguardmapminifier name strategy CL: https://r8-review.googlesource.com/c/r8/+/44542 Cherry pick: Do not statically merge classes with synchronized methods CL: https://r8-review.googlesource.com/c/r8/+/44227 Cherry pick: Classes with synchronized methods should not be merged vertically CL: https://r8-review.googlesource.com/c/r8/+/44226 Cherry pick: Update isStrict to isStatic CL: https://r8-review.googlesource.com/c/r8/+/44360 Cherry pick: Negate assertion regarding synchronized method CL: https://r8-review.googlesource.com/c/r8/+/44362 Cherry pick: Refactor static class merger merge into a single method CL: https://r8-review.googlesource.com/c/r8/+/44464 Cherry pick: Reland "Find set of lock-candidates from const-class to disallow in merging" CL: https://r8-review.googlesource.com/c/r8/+/44742 Cherry pick: Add utility to testbase for testing on current runtime CL: https://r8-review.googlesource.com/c/r8/+/44182 Bug: 142438687 Bug: 142909857 Change-Id: I9371099fccff6f480711774aca69aeb32dc0f873
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 firstname.lastname@example.org.