|author||Christoffer Quist Adamsen <email@example.com>||Wed Jun 09 15:56:53 2021 +0200|
|committer||Christoffer Quist Adamsen <firstname.lastname@example.org>||Wed Jun 09 13:57:48 2021 +0000|
Remove annotations from non-kept items in non-compat mode RELNOTES: Remove annotations from non-kept items in non-compat mode. When building with R8 in Proguard compatibility mode, R8 does not remove any annotations from the program that are matched by a `-keepattributes` rule (e.g., the `RuntimeVisibleAnnnotations` attribute). In non-compatibility mode (also called full mode), R8 now removes all annotations from the program, except annotations on classes, fields, and methods that are matched by a `-keep` rule. For example, to retain all runtime visible annotations for a class `C` it is no longer sufficient to add the rule '-keepattributes RuntimeVisibleAnnotations' in non-compatibility mode. The configuration must also explicitly add a `-keep` rule for class `C`, which can be done with the rule `-keep class C`, or the rule `-keep,allowobfuscation,allowshrinking class C`, which allows both renaming and shrinking of `C`, but still preserves the annotations of `C` if the class is not removed. Change-Id: Ife273adbcfa1c9a690fc905566b6a87c66353737
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.