| commit | 6053ac1816351a2534c1b2ce1187588c19a4e1d3 | [log] [tgz] |
|---|---|---|
| author | Hadrien Zalek <hzalek@google.com> | Tue Nov 22 15:40:26 2022 -0800 |
| committer | Hadrien Zalek <hzalek@google.com> | Tue Nov 22 15:40:26 2022 -0800 |
| tree | 5d31e51f3be18177af6e8152590b405fb3b4fb71 | |
| parent | 092073607de80221dcdd5aaa21611973160e6f6b [diff] |
Fix Java flags in TF template to work with JDK 17+ Isolated TF tests are failing since the `--add-exports` option cannot be parsed by JDK 17+ due to a missing '<target-module>' component. This change resolves the issue by adjusting the options in the TF template to export the source package to all unnamed modules. See https://docs.oracle.com/javase/9/migrate/toc.htm#JSMIG-GUID-2F61F3A9-0979-46A4-8B49-325BA0EE8B66 for more information. Test: atest --host HelloWorldHostTest Change-Id: Iccb8a8dcd3707237e018d6feb6b6a0e8d2bc9a86
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.