Skip to content
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

More dummy AWT methods #972

Merged
merged 1 commit into from
Jul 29, 2021
Merged

Conversation

jperedadnr
Copy link
Contributor

Issue

Fixes #970

Progress

@jperedadnr jperedadnr requested a review from johanvos July 29, 2021 18:30
@jperedadnr jperedadnr merged commit 5d9af84 into gluonhq:master Jul 29, 2021
@jperedadnr jperedadnr deleted the 970-androidawt-2 branch July 29, 2021 19:02
makingthematrix added a commit to makingthematrix/substrate that referenced this pull request Sep 8, 2021
This is a follow up to gluonhq#971 and gluonhq#972.

I made a minimal Android app with FXGL, the game engine which uses JavaFX. It turns out that GraalVM Native Image
adds many more unresolved references when compiling FXGL. I added the dummy methods for them to launcher.c.

With these changes my minimal app works  but I wonder if this is a good approach. All the methods I added have
something to do with image handling. What if, when I start to write a more complex app, GraalVM Native Image will
start adding even more references?

Here's my app: https://github.com/makingthematrix/scalaonandroid/tree/main/HelloFXGL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cannot locate symbol "JNI_OnLoad_awt"
2 participants