| commit | 97a9903c3e49731cb619f6992b99ac5d4a2df82e | [log] [tgz] |
|---|---|---|
| author | Jared Duke <jdduke@google.com> | Tue Aug 02 16:05:03 2022 -0700 |
| committer | Jared Duke <jdduke@google.com> | Wed Aug 03 08:35:45 2022 -0700 |
| tree | f4a4674a7228af7bdbda63161bf007372fdb3e43 | |
| parent | f68794510fcbfd10a38bdfbf8d5d6c1f6d206afb [diff] |
Refine VisibleForTesting proguard rules Both androidx (Jetpack) and com.google.common (Guava) define @VisibleForTesting annotations. These are used within these libraries for test purposes, but have also been adopted throughout the platform for platform-specific test code. Consequently, the current keep rules end up keeping not only platform test code, but also library test code that isn't actually needed. Refine these rules by restricting VisibleForTesting-annotated keep rules to include code *outside* of Jetpack/Guava. A longer term solution will involve migrating away from these annotations toward the platform-defined @TestApi and internal @VisibleForTesting variants. Note that platform code using the androidx* and c.g.common*-defined @VisibleForTesting annotations will still be kept. This saves about ~11MB of dex code from platform apps/services. Bug: 239961360 Test: m + validate dex changes for shrunk packages (SystemUI/Launcher) Change-Id: Icd70090e615b72a2cfb9ce8c43edb17cb46e05e2
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.