[Slackbuilds-users] [FIX] Eclipse + xulrunner issue.

[André Barboza]

> I've already send an eclipse SlackBuild update for version 3.6.2 to
> André Barboza (the current maintainer) but i have not the
> time-platform to test if its true what Grant Gayed stated in his
> posts. If someone can make some test in this aspect could be very
> helpful to "fix" this situation. Just build xulrunner *without* the
> use of "--enable-optimize" (or "--disable-optimize" if applies) and
> let eclipse decides the use of uxlrunner *without* your meddling
> [8][9][10]. And yes... i think that André Barboza solution (patch) its
> not the correct answer but maybe i could be wrong ;-)

The patch is NOT a solution itself, but as you said before: It's not
an eclipse bug.
I think what we can do is set MOZILLA_FIVE_PATH variable in the
startup script based on the user installation.
I chose check the xulrunner installation before everything, so I
anyone really wants the internal browser, they can build the xulrunner
with all requeriments of eclipse.

Maybe, we can put some tips of xulrunner building on the README
file... what do you think?

2011/5/13 Antonio Hernández Blas <hba.nihilismus at gmail.com>
>
> On Sun, May 1, 2011 at 2:00 AM, Bradley D. Thornton
> <Bradley at northtech.us> wrote:
>
> Hi Bradley:
>
> I've just took my time to search more about this issue and i conclude
> that actually it's not an eclipse bug, but rather the problem exists
> in the way xulrunner is builded.
>
> First, Eclipse's SWT Browser (it's internal web browser) uses
> xulrunner depending in its version [1], so the current Eclipse 3.6.x
> requires XULRunner 1.8.x - 1.9.2.x.
>
> And second, SWT can use xulrunner *just* if this was builded without
> it's optimization flag [2] and i have seen that Alien Bob's one [3]
> (SBo also [4]) uses "--enable-optimize="$CFLAGS" \"
>
> According with Grant Gayed it's really important to build xulrunner
> without the use of "--enable-optimize" [5] to get a functional eclipse
> browser (swt+xulrunner) both in x86 and x86_64. Also he makes another
> important question, ¿which platform of jre (and i add jdk) you use? If
> you use eclipse x86_64, then it would search for a jre/jdk x86_64 and
> a xulrunner x86_64. Important to know to avoid issues between them
> [6][7]
>
> [1] http://www.eclipse.org/swt/faq.php#browserlinux
> [2] http://dev.eclipse.org/mhonarc/lists/platform-swt-dev/msg06874.html
> [3] http://connie.slackware.com/~alien/slackbuilds/xulrunner/build/xulrunner.SlackBuild
> [4] http://slackbuilds.org/slackbuilds/13.37/libraries/xulrunner/xulrunner.SlackBuild
> [5] http://web.archiveorange.com/archive/v/rtUM3C62ZOKbXX0i2y9A
> [6] http://ubuntuforums.org/showthread.php?t=1263776
> [7] http://blog.javaee.cz/2009/11/ubuntu-910-64bit-and-custom-32bit-jdk.html
>
> >
> > When eclipse 3.6.1 hit, I went and installed it as soon as I could, long
> > before the warning notice in the README for the Slackbuild. I even
> > submitted a bug report to Eclipse, and got one response, several months
> > later asking a couple of questions that led nowhere.
> >
> > It seems they're clueless over at Eclipse to this bug, and my ticket is
> > still open after all these months.
> >
> > Maybe when the next version is released their bug will be fixed?
> >
>
> Actually i think that they know about this "bug", but its not in their
> hands to decide how a linux distribution builds xulrunner.
>
> >
> > For the time being, Eclipse 3.6.0 works fine, so my recommendation at
> > this time, for people running Slackware64, is to avoid installing 3.6.1
> > since this bug has not been addressed, and none of the kludges to fix it
> > seem to apply for 64bit OS.
> >
> > I'd be interested in hearing other perspectives.
> >
>
> I've already send an eclipse SlackBuild update for version 3.6.2 to
> André Barboza (the current maintainer) but i have not the
> time-platform to test if its true what Grant Gayed stated in his
> posts. If someone can make some test in this aspect could be very
> helpful to "fix" this situation. Just build xulrunner *without* the
> use of "--enable-optimize" (or "--disable-optimize" if applies) and
> let eclipse decides the use of uxlrunner *without* your meddling
> [8][9][10]. And yes... i think that André Barboza solution (patch) its
> not the correct answer but maybe i could be wrong ;-)
>
> [8] http://www.eclipse.org/swt/faq.php#specifyxulrunner
> [9] http://www.eclipse.org/swt/faq.php#howdetectmozilla
> [10] http://www.eclipse.org/swt/faq.php#printmozillapath
>
> --
> -
> hba | Antonio Hernández Blas | Mexico, Mx.
> http://hba.dyndns.info | http://barrapunto.com/~hba/ |
> irc://irc.freenode.org/hba
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>