jfxrt.jar - is it platform specific?

[Daniel Zwolenski]

Ok, thanks.

Is it architecture specific, i.e. within a target OS does each platform
require it's own jfxrt.jar or do they all share the same? Most
specifically, on iOS do the armv7 and i386 architectures use the same JAR
and just different lib files or is there a specific jfxrt.jar for each?

In general it would be great to see a list of all the distinct JARs that
can be produced e.g. something like:

jfxrt-ios.jar
jfxrt-win.jar (or is jfx-win32.jar and jfx-win64.jar, etc)
jfxrt-osx.jar
jfxrt-linux.jar
jfxrt-pi.jar

I imagine that list is very wrong (pi, linux, especially) - what's the real
list? This (https://wiki.openjdk.java.net/display/OpenJFX/Building+OpenJFX)
kind of hints at it but for example if I want to build for win32 do I have
to be on a win32 system or does building on a 64 bit platform produce the
files needed for both, etc?

Even better if we had some document that outlined all the supported
platforms the JAR and the native libs built for that platform in a nice big
table. Bonus points for clear cut steps and commands to build each one,
which platforms you can run on and what gradle command to run.




On Thu, Jul 25, 2013 at 3:32 PM, Kevin Rushforth <kevin.rushforth at oracle.com
> wrote:

> Yes, jfxrt.jar is platform-specific. On the desktop there are
> platform-specific glass and Prism classes (not sure about the WebKit
> classes). On embedded platforms (Linux-arm, IOS, Android) there are many
> differences.
>
> -- Kevin
>
>
>
> Daniel Zwolenski wrote:
>
>> Obviously there are native libs (dlls, etc) that JFX uses that are outside
>> of the jfxrt.jar.
>>
>> But is the actual jfxrt.jar produced by the build generic and able to be
>> used on any platform (so long as the natives are also present) or is it
>> platform specific itself?
>>
>> We are getting close to the ios/backport stuff working (as well as it can
>> at this stage) and are aiming to start putting stuff in Maven soon. Just
>> want to make sure I get the separations as clean as possible because once
>> it's in Central it doesn't ever leave.
>>
>> Cheers.
>>
>>
>