This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: Location of the JavaFX runtime library
- From: Per Bothner <per at bothner dot com>
- To: Weiqi Gao <weiqigao at gmail dot com>
- Cc: kawa at sourceware dot org
- Date: Wed, 30 May 2012 20:56:17 -0700
- Subject: Re: Location of the JavaFX runtime library
- References: <E41A6AC0-ABF3-4A72-B1DE-24D00DFEDC73@gmail.com>
On 05/30/2012 05:32 PM, Weiqi Gao wrote:
Per,
For people who use JDK 7u4 on the Mac, the jfxrt.jar is located inside the JDK under jre/lib/jfxrt.jar. The current --with-javafx configuration script expects the structure of a standalone JavaFX SDK where it is under rt/lib/jfxrt.jar. Can the configuration script be changed to accommodate both situations?
I think the case where we're using the JavaFX bundled with JDK or JRE
should be handled by *not* setting the classpath.
I.e., when using configure,
--with-javafx (wth no path) should mean to enable JavaFX, but without
changing
the claspath
--with-javafx=PATH/jfxrt.jar should mean enable JavaFX, and set
$conf_classpath to include the specified jar.
For backward compatibility, the previous form should check whether
PATH/jfxrt.jar or PATH/rt/lib/jfxrt.jar exist. I.e. if the former
doesn't exist, but the latter does, use the latter interpretation.
At some point we might want to make --with-javafx the default - though
perhaps not unless building for Java 8.
Ant builds should do something similar, but could perhaps default
to enabling javafx if a suitable marker class (say javafx.scene.Node)
exists.
--
--Per Bothner
per@bothner.com http://per.bothner.com/