Please review this fix to add a GPLv2+Classpath copyright header to
those javafx.web native files that are missing the header.
https://bugs.openjdk.java.net/browse/JDK-8209086
https://github.com/javafxports/openjdk-jfx/pull/533
-- Kevin
Regarding the GTK3 dependency, I filed JDK-8227808 [1] a couple days ago
to fail at build time if the GTK3 libraries aren't present, rather than
generating a library that doesn't run. I also just updated the Wiki.
-- Kevin
[1] https://bugs.openjdk.java.net/browse/JDK-8227808
On 7/17/2019
I see that Tom Schindl filed the Enhancement request.
https://bugs.openjdk.java.net/browse/JDK-8228357
-- Kevin
On 7/17/2019 11:08 PM, Tom Eugelink wrote:
Hm. Being able to just debug JavaFX will seriously lower the threshold
for people to get on board. Personally if I run into a library
as requested by Kevin - https://bugs.openjdk.java.net/browse/JDK-8228357
- I filed in in the other category because i could not find a better
matching one.
Tom
On 18.07.19 08:18, Robert Lichtenberger wrote:
> I started from scratch today and was able to compile and use JavaFX with
> debug
I started from scratch today and was able to compile and use JavaFX with
debug information.
When trying to start the test application an error was thrown: no glassgtk3
in java.library.path;
Now thanks to the debugging information beeing present I was able to debug
GtkApplication like a charm and
Hm. Being able to just debug JavaFX will seriously lower the threshold for people to get
on board. Personally if I run into a library that is behaving faulty and I need to
download and compile it first, I'm already not very happy (it's a hassle). But ahm...
cygwin, visual studio, directshow
