forked from CAIDA/walrus
-
Notifications
You must be signed in to change notification settings - Fork 3
/
BUILDING
99 lines (65 loc) · 3.12 KB
/
BUILDING
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
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
=============================================================================
BUILDING WALRUS
=============================================================================
REQUIREMENTS
At a minimum, you'll need Java3D v1.2.1 (or later), JDK1.3.0 (or later),
and GNU Make.
Java3D: http://java.sun.com/products/java-media/3D/index.html
JDK: http://java.sun.com/j2se/
* Mac users:
You'll need at least a 2-button mouse (3 buttons are preferred).
Download Java3D from
http://www.apple.com/downloads/macosx/apple/java3dandjavaadvancedimagingupdate.html
* Windows users:
Be sure to use the OpenGL version of Java3D and not the DirectX version,
which has problems.
* Linux users:
We, as well as others, have had problems running Java3D on an NVIDIA card.
Using JDK 1.4 and Java3D 1.3.1beta seems to help, but you may still
experience instability.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
COMPILING
Walrus classes are declared in the top-level anonymous package, so you
can unpack the source distribution anywhere.
To build Walrus, the following items must be added to your CLASSPATH:
libsea.jar,
antlrall-mod.jar,
mp.jar, and
the directory containing the Walrus source files.
For example, if the Walrus source distribution has been unpacked into the
directory /home/me, then the items to add to your CLASSPATH are
/home/me/walrus-0.6.3-src/libsea.jar
/home/me/walrus-0.6.3-src/antlrall-mod.jar
/home/me/walrus-0.6.3-src/mp.jar
. [a period, representing the 'current directory']
Under UNIX, you would do something like the following (the exact
syntax is dependent on your shell):
CLASSPATH=$CLASSPATH:/home/me/walrus-0.6.3-src/libsea.jar:/home/me/walrus-0.6.3-src/antlrall-mod.jar:/home/me/walrus-0.6.3-src/mp.jar:.
export CLASSPATH
The '.' at the end of the above CLASSPATH ensures that Java can find
the Walrus source/class files.
Now, update the configuration options in Makefile.nodep, if necessary,
and execute
$ make -f Makefile.nodep
The above procedure will compile all the Walrus classes, and Walrus will be
ready for use.
When actually doing development work, it's more convenient and less
error-prone to have makefile dependencies automatically generated for you.
This mechanism is implemented in 'Makefile' using the IBM Jikes compiler
(however, the actual compilation of source files to bytecode is done with
your platform's Java compiler rather than with Jikes, although nothing
prevents you from using Jikes for both tasks).
You can download Jikes from
http://jikes.sourceforge.net/
You do not need to install Jikes if you simply want to build Walrus
from the source, since the source distribution contains a copy of the
dependency files (*.u) that can be used so long as no source file is
ever modified.
After installing Jikes, update the configuration options in Makefile,
if necessary, and build Walrus with
$ make
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
DOCUMENTATION
See 'docs/classdiagram.jpg' for the relationships between key classes in the
implementation.
For running Walrus, see README.RUN.