It’d be more helpful to know what the NSException was. Without that
information, it’s nearly impossible to figure out what’s going on from the
stack trace alone. Debug symbols would help too, but if you’re using Java
Packager that won’t be an option (sounds like an RFE waiting to happen..).
Whi
Hi,
Thanks for your suggestion. Unfortunately, I don't believe it's a mix between
32 and 64 bit libraries.
In the sandboxed version I distribute, binaries are built with an Ant script
which removes the 32 bit version of libraries with lipo.
Doesn't the stack trace give some hints to some of you
looking at your build.xml on CVS browser . . possible you are using 32 bit
JOGL libraries . .you will want to update all your native binary libraries
for OSX to 64 bit .. that's just what jumped out I haven't looked at the
whole file ..
215 216 218 219 220 221 222 223 224 225 226 227
What version of the javafxpackager? Try using the latest in the 8u40 EA builds
if you haven't already. You should still be able to bundle Java 7 with it if
your app doesn't run with 8.
-DrD-
> Thank you all for your suggestions.
> Just to be clear, this error happens for very few users in a sa
Thank you all for your suggestions.
Just to be clear, this error happens for very few users in a sandboxed version
of the program that embeds a copy of the JRE.
The error happens with JavaAppLauncher and with the launcher provided with
javafxpacakager.
Nevertheless, I requested to a user who enco
