From: Arie van Wingerden <xapwing@gmail.com>
To: chaw@eip10.org
Cc: kawa@sourceware.org
Subject: Re: How to access JavaFx class library from Kawa?
Date: Sun, 28 Oct 2018 14:21:00 -0000 [thread overview]
Message-ID: <CADkALSHh-FSmUaTQ7_tbxtL0_yRooUpUMnRH-VRmHH40c-FLwQ@mail.gmail.com> (raw)
In-Reply-To: <10215.1540734221@vpaur.eip10.org>
Hi Chaw,
thx!
Now tried this:
set CLASSPATH=E:\Programs\openjdk\lib\*;E:\Programs\openjfx\lib\*;.\*
last one is for jars in current dir.
But it still fails because it cannot find javafx/geometry/Orientation.
In openjfx\lib I see:
javafx-swt.jar
javafx.base.jar
javafx.controls.jar
javafx.fxml.jar
javafx.graphics.jar
javafx.media.jar
javafx.properties
javafx.swing.jar
javafx.web.jar
src.zip
But no "geometry" or similar.
/Arie
Op zo 28 okt. 2018 om 14:43 schreef Sudarshan S Chawathe <chaw@eip10.org>:
> > when trying to run your JavaFx example from here:
> > https://per.bothner.com/blog/2011/JavaFX-using-Kawa-intro/ I get errors
> > like: Exception in thread "main" java.lang.NoClassDefFoundError:
> > javafx/geometry/Orientation.
> >
> > This is understandable, since I only unpacked JavaFx in a folder, but I
> > don't know how to inform Kawa how to find JavaFx stuff.
>
> If you set CLASSPATH for Java one way or the other (environment
> variable, command-line option, ...) to include the JavaFX .jar files
> then you should be able to use JavaFX from Kawa as well. At least, that
> has been my experiance on a standard Debian-based setup.
>
> The CLASSPATH syntax allows using "*" to indicate "all jars in
> directory" which I find useful in such cases to avoid having to
> enumerate jars individually.
>
> Regards,
>
> -chaw
>
>
next prev parent reply other threads:[~2018-10-28 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 12:56 Arie van Wingerden
2018-10-28 13:43 ` Sudarshan S Chawathe
2018-10-28 14:21 ` Arie van Wingerden [this message]
2018-10-28 15:18 ` Sudarshan S Chawathe
2018-10-28 15:19 ` Arie van Wingerden
2018-10-28 15:22 ` Arie van Wingerden
2018-10-29 7:22 ` Arie van Wingerden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADkALSHh-FSmUaTQ7_tbxtL0_yRooUpUMnRH-VRmHH40c-FLwQ@mail.gmail.com \
--to=xapwing@gmail.com \
--cc=chaw@eip10.org \
--cc=kawa@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).