[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [linuxtools-dev] Run SDK JUnit tests and post results to wiki
|
On 07.10.2009 23:55, Andrew Overholt wrote:
* Matthias Klose<doko@xxxxxxxxxx> [2009-10-07 17:06]:
On 07.10.2009 22:43, Andrew Overholt wrote:
I have one issue, though: headless support. I wrote runtests.sh to
look for Xvnc in /usr/bin or /usr/bin/X11 (old). I couldn't find either
of these binaries in a Debian package.
I never used vnc on a buildd, all packages which need X on during the
usually run xvfb-run<command>
If you want to run the tests as part of the build, then this seems like
the best option. I was more concerned about running them on an
arbitrary Debian system so that they wouldn't be affected by the main
DISPLAY.
Another issue I found is that I don't think the internal SWT browser is
working. I get white background welcome screens which is a sign that
it's not working. Is there some sort of LD_LIBRARY_PATH mucking we need
to add somewhere? Perhaps a patch to SWT to make it look in the right
place? I can't imagine it just _doesn't_ work on Debian unstable so
maybe it's my virtual machine?
On Ubuntu this works by explicitely setting the LD_LIBRARY_PATH to
/usr/lib/xulrunner-1.9.1.3
This just means that someone needs to investigate how SWT is looking for
the XR libraries and see why it's not finding the Debian/Ubuntu
installation location.
yes, Alexander will followup on this, for now a wrapper script will do:
#! /bin/sh
xuldir=/usr/lib/xulrunner-$(/usr/bin/xulrunner --gre-version)
LD_LIBRARY_PATH=$xuldir${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} exec
/usr/bin/eclipse-bin "$@"
Note that eclipse may be built against another xuldir than it is run. I did see
in the error message about not finding the internal browser, that
MOZILLA_FIVE_HOME is set to /usr/lib64/xulrunner-addons, which doesn't contain
the xulrunner libs.
Matthias
