You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a small Hello-World-Kind JavaFX Application for Testing Gluonhq-GraalVM to check if my setup is in working order.
I am using:
Gradle 7.3
Java 17
GluonHQ-Graalvm version 22.0.0.3
org.openjfx.javafxplugin: version 0.0.11
com.gluon.gluonfx-gradle-version-plugin: version 1.0.12
Everything works under Linux, but when trying the same project under windows 10: nativeCompile fails with fatal error:
the download of openjfx-18ea+10-windows-x86_64-static.zip fails, since the file cannot be found on https://download2.gluonhq.com/substrate/javafxstaticsdk
So it seems there are files missing or wrongly named on the gluonhq server.
The text was updated successfully, but these errors were encountered:
Update:
setting the javafxStaticSdkVersion to 17 in the gradle gluonfx section made the above error disappear.
Now nativeBuild claims to work, but nativeRun (and running the exe directlly from the command llne) does nothing. No JavaFX window appears, but the programm (nearly 60 MB) claims to have run succesfully. The standard JVM run works fine.
18-ea+10 is back, there was a small glitch... As for the error with 17 (no window) you will have it probably with 18-ea+10 too.
I suggest you run your executable with:
I have a small Hello-World-Kind JavaFX Application for Testing Gluonhq-GraalVM to check if my setup is in working order.
I am using:
Gradle 7.3
Java 17
GluonHQ-Graalvm version 22.0.0.3
org.openjfx.javafxplugin: version 0.0.11
com.gluon.gluonfx-gradle-version-plugin: version 1.0.12
Everything works under Linux, but when trying the same project under windows 10: nativeCompile fails with fatal error:
the download of openjfx-18ea+10-windows-x86_64-static.zip fails, since the file cannot be found on
https://download2.gluonhq.com/substrate/javafxstaticsdk
So it seems there are files missing or wrongly named on the gluonhq server.
The text was updated successfully, but these errors were encountered: