-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incomplete setup for jdk+fx on ubuntu-latest (?) #120
Comments
I found a workaround with a conditional step, that allows me to compile (binary testing is pending):
Nonetheless, I'm wondering it that should be required or of one could expect this to work out of the box.... |
Hi @rvullriede, You mentioned that you only got this working with Liberica and that's probably only because they ship reachability metadata for AWT. It should also work with other distributions, like GraalVM CE or Oracle GraalVM, if you use the Tracing Agent to collect reachability metadata for your application. This can arguably be a bit annoying because you'd need to run it on all platforms as AWT is platform-specific. However, the metadata in Liberica is not specific to your app and may very well pull in a lot more code than actually is needed. So if you use the tracing agent, you may even get smaller binaries. Here's a blog post that explains how to do this on Windows: Hope this helps! |
I have a small JavaFX app and researched quite a bit for a reliable way to compile this to native using GraalVM. It's worth noting that the app uses a tiny bit of good old AWT to configure the Taskbar icon.
I've tried a multitude of combinations of:
each in combination with:
The only working solution (including the tiny AWT piece) is:
I've set this up using Github Actions using the following config:
for the following os:
This works without any problems for macos-14, macos-13, windows-latest but it fails for ubuntu-latest with the following error:
You'll find the complete action here:
https://github.com/osslabz/log-gazer/blob/dev/.github/workflows/build-release-on-main-push.yml
and the complete run log here:
https://github.com/osslabz/log-gazer/actions/runs/12242211892/job/34149026394
I'm not quite sure if this is actually a problem with graalvm/setup-graalvm or maybe with the OS image itself or the Libernica NIC but since the setup is identical for all OS I'd naively assume it should work the same for all.
If you think this should be better addressed somewhere else, please point me to the right direction, thanks!
The text was updated successfully, but these errors were encountered: