-
Notifications
You must be signed in to change notification settings - Fork 62
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
Graal AOT compilation not working, probably due to the JFX plugin #156
Comments
I wrote a project that worked through JavaFX's media module, Native Image, and was working with the media module. If you are interested, you can come to my Repository: |
That's not a Gradle project. Maven works just fine as I've described in my OP. |
Hi, I thought this could only be accomplished with https://github.com/gluonhq/gluonfx-maven-plugin/ Thanks |
not sure if i have the exact same problem, but somehow feels its going to the same direction:
the source is available at https://gitlab.com/olze/chatclient - i am kinda lost and give up with graalvm for now (again...) |
I have reason to believe that there is a problem with the javafx-gradle-plugin that causes it not to work with Graal Native.
To compile a JavaFX application natively, one usually needs to run an application with Graal's tracing agent to generate configuration files that can then be provided to the Graal compiler.
This works with both Maven and even Scala's sbt, but when doing this with a Gradle project, this error occurs:
Graphics device initialization failed for : d3d, sw
or ratherGraphics device initialization failed for : es2, sw
.Gluon will tell you to use the Gluon plugin instead of the Graal plugin, but that shouldn't be necessary at all, because as I mentioned before, it works with both sbt and Maven and even with Gluon's Gradle plugin it won`t work and you have to switch to SWRendering.
The text was updated successfully, but these errors were encountered: