Building x11-toolkits/swt-devel with libxul gecko provider
Robert Noland
rnoland at FreeBSD.org
Sun Sep 27 14:48:23 UTC 2009
On Sun, 2009-09-27 at 16:08 +0200, Beat Gaetzi wrote:
> Hi Robert,
>
> We are going to remove xulrunner, Firefox 2 and Mozilla from the ports
> tree. We created a patch which switches all ports using xulrunner,
> firefox or mozilla gecko provider to libxul.
> Unfortunately three ports failed during the exp-run. One of them is
> x11-toolkits/swt-devel which is maintained by you. I tried to fix this
> problem but was not successful.
> Could you please take a look at this problem. Is it possible to use
> swt-devel with libxul gecko provider? If not, should we remove the port?
so, I have updated ports of both swt and swt-devel that use libxul. swt
actually builds a seperate library for libxul support, so I've been
trying to decide the best way to deal with it. I have been thinking of
going ahead and dropping traditional GECKO support, but the primary
consumer of swt that I know of is vuze. In vuze, you have to
specifically configure it (runtime config setting) to use libxul, which
I can just add a note to pkg-message about. The primary issue that I've
been hoping would get fixed is that a search in vuze doesn't show any
results when using libxul. Everything else works properly. The vuze
guys indicated that it is a bug in swt, but it persists. The feature
still works correctly with traditional GECKO support, so I was resisting
a forced move to libxul.
Both ports are more or less ready to commit though... As well as an
update to vuze...
robert.
> Patch which was tested on pointyhat is available here (updated version
> for current ports tree):
> http://tmp.chruetertee.ch/gecko-ff-removal-part2-v0.3.patch
>
> Pointyhat log is here:
> http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/a.7-exp.20090917174615/swt-devel-3.5.m6_1,1.log
>
> Thanks,
> Beat, on behalf of the FreeBSD-Gecko Team
>
--
Robert Noland <rnoland at FreeBSD.org>
FreeBSD
More information about the freebsd-gecko
mailing list