On 05/16/2018 10:42 AM, Kevin Rushforth wrote:
On 5/15/2018 11:57 PM, Ty Young wrote:
3. JavaFX has been removed from JDK 11 as of this week. Starting
with jdk-11+14, early access builds of JDK 11 will not include JavaFX.
I'm not sure if it's intentional or perhaps a bug on my end, but I
cannot compile JavaFX without Oracle JDK(9 or 10). Attempting to do
so with a self compiled JDK with JavaFX support results in a build
fail while doing it without JavaFX entirely results in a fail due to
Observable classes being missing.
Is Oracle JDK a requirement for building JavaFX currently or is this
just some weird bug with my compiled JDK?
This is likely something on your end, since we build the standalone
JavaFX using OpenJDK 10. What repo are you building from? The correct
repo is:
http://hg.openjdk.java.net/openjfx/jfx-dev/rt
That one, as mentioned in the wiki build guide. I get an immediate build
fail(see: https://pastebin.com/geR4LLMm). The JDK works just fine: I can
set it as the default JDK, run Netbeans, set the project source to 11,
and my application builds just fine.
And could the new standalone modules be integrated with the source
code somehow so that a JDK without JavaFX support can be compiled?
Not sure what you mean, but you can use an OpenJDK without modules +
the JavaFX standalone modules to build and run your program.
It's an option, sure. My problem with it is that it creates so much
unnecessary disk usage because each bundled application requires it's
own copy of JavaFX. If you had 10 standalone JavaFX applications it
would be 1GB easily if they where all modular projects, which are around
106MB for me. Creating an app bundle using classpath is around
200MB(post JDK 8 was 250+ IIRC).
As I wrote before and am still having issues with, after a successful
first compile, JavaFX no longer compiles in Arch Linux for me. Any
attempt to do so results in a bunch of warning messages(see:
https://pastebin.com/rJqu7Nws) which cause the build to fail due to
warnings being treated as errors(Should they even be ignored?). In
addition. I'm now getting a GCC warning about XIMProc returning an
int when it should return void (*). I don't know C or the native APIs
so right now I'm at a loss of what to do besides trying to compile on
another distro - which is something I *really* would prefer not to
have to do.
What gcc version are you using? And what Linux distro?
8.1.0 and Arch Linux(Antergos which is basically Arch Linux).
-- Kevin
