| commit | db6557e490468bfe86dfe082710a2c5b7149ed84 | [log] [tgz] |
|---|---|---|
| author | Jeff Gaston <jeffrygaston@google.com> | Tue Feb 27 14:05:40 2018 -0500 |
| committer | Jeff Gaston <jeffrygaston@google.com> | Wed Mar 28 23:00:02 2018 +0000 |
| tree | cbf8eae2f61b8ca4799c59e2991529b7955020f6 | |
| parent | ac1109733dfd87024693bcbd821c99cdee5c8875 [diff] |
Run jetifier against prebuilts directly rather than classes.jar
It turns out that the resource files inside the .aar files may
need rewriting too
Bug: 72552006
Test: Set LOCAL_JETIFIED_ENABLED for a prebuilt and built it
See also one of the patches after this one and its topic
which contains a sample for testing
Change-Id: I89d0b4aa8d5c6ae3abc2344dd05222cf9672d5c0
(cherry picked from commit ed170e72961dab855848bc58527923cbeba551b5)
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.