| commit | 041e78342a46f0f0fe4f5a0499139934adc0f7e2 | [log] [tgz] |
|---|---|---|
| author | Rex Hoffman <rexhoffman@google.com> | Tue Jan 28 06:34:51 2025 +0000 |
| committer | Rex Hoffman <rexhoffman@google.com> | Tue Jan 28 14:12:22 2025 +0000 |
| tree | 76546a2c9f3ddf3b1437258a9e0712da46cef2b7 | |
| parent | 3617bc1fc20beaff6de5ed7c272b69e434ec3ef1 [diff] |
Set JAVA_HOME for runtime via soong AndroidTest.xml template
The jdk used by Robolectric during tests should always be the ANDROID_JAVA_HOME, as such this change, reads that environment variable from the build, and uses it to set the java_folder via the {EXTRA_CONFIGS} in the build/core/robolectric_test_config_template.xml
Test: atest MyRoboTests and look at the generated xml file
Bug: 372520027
Change-Id: Ie63da8602224279f7920c124762cfc29f714c7e1
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.