Grant,
I'm running on a 64-bit debian lenny build.
1. That's why I figured 1.9.1.8 would be a safer bet on a non-HEAD branch, but it didn't work either. I could drop back to the stable versions, but I was assuming nothing cutting edge was happening on the 1.9.1 branch. And it had the exact same behavior on both branches.2. I'm using the SWT HEAD, so that shouldn't an issue 3. Oh, I'm sure it's finding some Mozilla, probably the Iceweasel one I have installed. I don't have any other type of browser on my linux box. 4. Definitely, "Java HotSpot(TM) 64-Bit Server VM", 1.6.0_12-b04 5. I used the default "minimal .mozconfig" from the website instructions with a "--java-include-path" option since it was being stubborn about finding my JAVA_HOME. I definitely didn't use "--disable-optimize". Would that affect the behavior or just help me debug a problem?
Thanks, Ryan On Feb 2, 2010, at 10:01 AM, Grant Gayed wrote:
Hi,
Which platform are you using? This
definitely should work on 64-bit linux, but not 64-bit Windows or OSX since
64-bit builds of XULRunner are not available for these configurations.
Eclipse does not ship a XULRunner, so if the Browser works for you
when you don't point at a specific XULRunner install then it is finding
a usable native brower on your machine. Some possibilities to consider:
1. Only use XULRunner "final"
releases, not betas (eg.- 1.9.2 is a final release, but 1.9.2pre is not).
2. Note the supported swt->xulrunner
versions: http://www.eclipse.org/swt/faq.php#browserlinux .
3. To determine which native browser
is being auto-detected when you don't point at a specific xulrunner run
a snippet like http://www.eclipse.org/swt/faq.php#printmozillapath .
4. Are you definitely running with a
64-bit JRE? If not then it will want to use a 32-bit XULRunner.
5. Which options did you specify in
your .mozconfig when compiling XULRunner? In particular, --disable-optimize
is an important one.
HTH,
Grant
Have other people had success running a 64-bit SWT
build with a 64-bit XULRunner? I built them both from source (since
neither is freely available) and I've tested them both separately and they
both seem to work without problems in general, but when I point SWT directly
to that XULRunner build, all I get is a blank browser window and no error
messages, then on dispose I get a XPCOM error -2147467262. This is
both with XULRunner 1.9.2.2pre and 1.9.1.8pre. The browser in the
SWT build works fine when using the default browser (which I assume it's
pulling from the Eclipse I'm using)._______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
|
