JavaFX with GraalVM

[Johan Vos]

That works (more or less).
In general, the build JVM determines what Java bytecodes are used. The
native libraries are pulled from static builds we generate.
We're working on supporting a number of configurations.

- Johan

On Tue, May 28, 2019 at 4:53 PM Michael Paus <mp at jugs.org> wrote:

> This is really great news. I am excited to see how this goes on.
> I have one question though: Is it really necessary to build on a JDK 11
> distribution or is it also ok to use JDK 12 and only set Source/Target
> to 11?
> - Michael
>
> Am 28.05.19 um 14:15 schrieb Johan Vos:
> > Hi,
> >
> > We just posted a news entry announcing that we have a build tool that
> > converts JavaFX applications into native executables using GraalVM:
> > https://gluonhq.com/a-boost-for-java-on-the-client/
> >
> > The JavaFX code used for this comes from my fork at
> > https://github.com/johanvos/openjdk-jfx/tree/omega which has only 1
> commit
> > that is not upstream (yet), and that allows to build static libraries
> from
> > the JavaFX code (instead of dynamic libraries).
> >
> > The source for the native parts of the Java core classes that are linked
> > into this release come from OpenJDK, where we built native libraries as
> > well (instead of dynamic libraries).
> >
> > At this moment, we only do this for Mac, but Linux is almost ready too,
> and
> > other platforms will follow.
> >
> > - Johan
>
>
>