| commit | 099349bea82f06d8733b1c75c9aa9aff2b4be854 | [log] [tgz] |
|---|---|---|
| author | Benjamin Peterson <benjamin@engflow.com> | Thu Jan 19 18:00:54 2023 +0000 |
| committer | Benjamin Peterson <benjamin@engflow.com> | Thu Jan 19 18:17:08 2023 +0000 |
| tree | 49180e43a8591b338e5e0113b4b9b80366f903b4 | |
| parent | 529aa1281755c6e93483b30a507edd2b893b91ab [diff] |
Fix remote execution of r8 and d8 in make 1. The location of the r8.jar and d8.jar files was no longer correct. 2. $(JAVA) was not defined before rbe.mk was included. 3. $(JAVA) includes options, which much be stripped to be a rewrapper toolchain input. Test: ran against an RBE cluster with RBE_D8_EXEC_STRATEGY=remote and RBE_R8_EXEC_STRATEGY=remote Change-Id: Icf434f5c0fda687c70c75b01b0bfd63bcd8cc474
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.