| commit | d2ba724f7f4a12ea68f5bb15e9b5e1580859e922 | [log] [tgz] |
|---|---|---|
| author | Jeff Gaston <jeffrygaston@google.com> | Wed Jan 31 17:34:07 2018 -0500 |
| committer | Jeff Gaston <jeffrygaston@google.com> | Tue Feb 20 22:25:23 2018 +0000 |
| tree | 726ef4ec64e7b413582bf66c92dc76ef00365d41 | |
| parent | 74e5ccb28bfc28b58a757740cd848b18e3ea04eb [diff] |
Add rule to enable running Jetifier within Make against Java modules
The only case where we expect to actually enable this behavior is for
modules that are just an unpacking of a prebuilt, because those are
the only cases for which we can't conveniently just change the source
Bug: 72552006
Test: ./build/soong/scripts/diff_build_graphs.sh \
--products=aosp_arm 'build/make:work^' \
'build/make:work'
Test: cherry-pick the following patch that depends on this one and
the rest of that patch's topic, and then do `m -j jeffapp`
Change-Id: I62e231900d6d87673ddf19c7fc2686fef2828590
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.