Community
Participate
Working Groups
In my local build, it appears SWT's internal browser doesn't work because it can't see the XR libraries: No more handles [MOZILLA_FIVE_HOME='/usr/lib/xulrunner-devel-1.9'] (java.lang.UnsatisfiedLinkError: no swt-mozilla-gtk-3555 or swt-mozilla-gtk in swt.library.path, java.library.path or the jar file) The compilation of the JNI SWT XR .so didn't give any errors ...
Fixing this would also allow Debian/Ubuntu to drop the LD_LIBRARY_PATH munging in their wrapper script.
This bug is still valid in eclipse-build 0.5.0 on Debian and Ubuntu.
Benjamin, do eclipse.org drops work out of the box on Debian?
The eclipse classic from eclipse.org works out of the box on Debian. For the Debian/Ubuntu package build with eclipse-build, we have to set MOZILLA_FIVE_HOME.
Do you have to set MOZILLA_FIVE_HOME at build time or run time or both?
I have to set in on runtime.
I don't know what's going on here but it requires some more investigation from the Debian and Ubuntu packagers.
Can this be introduces by a patch from eclipse-build?
If it is introduced by an eclipse-build patch, I suggest iterating over the SWT patches and selectively applying/building to see if it's true.
As xulrunner is pretty much obsolete now can we close this one?
Noone interested in supporting xulrunner for very long time. Closing.