blob: 4426c2c8ca2bb4d0d7e63f2fe15ea7e6167c1ab2 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
======== Instructions for >=dev-java-swt-3.2.2-r1 =========
To run the test, execute runtest2.sh
The test should load http://www.eclipse.org to a window. This window does not
seem to close properly so just pkill -9 java if you don't have anything else
java running.
You should test swt built agains firefox, seamonkey and xulrunner (if applicable)
by remerging with various USE flags. It can be built and only against one of the
three, so specifying multiple flags will result in effectively one, with this
priority:
xulrunner > firefox > seamonkey
So the test scenario for version that supports all three could look like this:
USE="seamonkey -firefox -xulrunner" emerge swt
runtest2.sh
pkill -9 java
USE="firefox -xulrunner" emerge swt
runtest2.sh
pkill -9 java
USE="xulrunner" emerge swt
runtest2.sh
pkill -9 java
======== Instructions for <=dev-java-swt-3.2.2 =========
runtest.sh takes one argument that is the browser implementation swt was built
against. So for examples:
runtest.sh xulrunner
(xulrunner) is the default
The test should load http://www.eclipse.org to a window. This window does not
seem to close properly so just pkill -9 java if you don't have anything else
java running.
You should test both seamonkey and xulrunner, like this:
USE="seamonkey -xulrunner" emerge swt
runtest.sh seamonkey
pkill -9 java
USE="xulrunner -seamonkey" emerge swt
runtest.sh xulrunner
pkill -9 java
(if you put both in USE, it builds against xulrunner)
|
GitWeb
