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
|
Installing GNU Classpath - Last updated: Feb. 07, 2002
First, this is a development release only! Unless you are interested in
active development and debugging, or just like running random alpha code,
this release is probably not for you. Please see the README file for a
list of VMs that work with GNU Classpath.
------------------------------------------------------------------
Suggested Software
------------------------------------------------------------------
For any build environment involving native libraries, these
new versions of autoconf, automake, and libtool are required.
- GNU autoconf 2.52
- GNU automake 1.5
- GNU libtool 1.4.2
For building the Java bytecode (.class files)
- IBM jikes 1.13 (newer versions up to 1.15 appear to be broken)
or GCJ 3.0.2+. The kjc compiler is supported with configure
but we have been unable to successfully compiled with it.
Jikes is currently the default compiler. You can select the
compiler using --with-jikes, --with-gcj or --with-kjc as argument
to configure.
Note that GCC 3.1 (from CVS) is currently broken, if you do
want to use it look at the status of the following bug:
<http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&database=gcc&pr=4715>
Applying the patch in that report to gcc/jva/parse.y does seem to
solve/work around the problem.
For building the JNI native libraries, the following are required.
- gcjh from GCJ 2.96+, others can be specified using
--with-javah=<program> as an argument to configure but have
not been tested and may not work
- GTK+ 1.2.x
- libart_lgpl 2.1.0
- gdk-pixbuf (Only needed if you want to compile the native library)
This package was designed to use the GNU standard for configuration
and makefiles. To build and install do the following:
1). Run the "configure" script to configure the package. There are
various options you might want to pass to configure to control how the
package is built. Consider the following options, "configure --help"
gives a complete list.
--enable-java compile Java source default=yes
--enable-jni compile JNI source default=no
--enable-cni compile CNI source default=no
--enable-load-library enable to use JNI native methods default=yes
(disabled automatically using --enable-cni)
2). Type "make" to build the package. There is no longer a
dependency problem and we aim to keep it that way.
3). Type "make install" to install everything. This may require
being the superuser. The default install path is /usr/local/classpath
you may change it by giving configure the --prefix=<path> option.
Report bugs to classpath@gnu.org or much better via Savannah at this
URL: http://savannah.gnu.org/support/?func=addsupport&group_id=85
Happy Hacking!
Once installed, GNU Classpath is ready to be used by any VM that supports
using the official version of GNU Classpath. Simply ensure that
/usr/local/classpath/share/classpath is in your $CLASSPATH environment
variable. You'll also have to set your LD_LIBRARY_PATH
variable (or similar system configuration) to include the Classpath
native libraries in /usr/local/classpath/lib/classpath.
*NOTE* All example paths assume the default prefix is used with configure.
If you don't know what this means then the examples are correct.
LD_LIBRARY_PATH=/usr/local/classpath/lib/classpath
CLASSPATH=/usr/local/classpath/share/classpath:.
export LD_LIBRARY_PATH CLASSPATH
More information about the VMs that use GNU Classpath can be found in the
README file. Information on using the above setup with the ORP VM can be
found at <http://www.gnu.org/software/classpath/doc/orp.html>.
------------------------------------------------------------------
Misc. Notes
------------------------------------------------------------------
Use of Sun's compiler is deprecated and probably does not work. At
least three free compilers are supported: gcj, jikes, and kjc.
Recompilation may cause a lot of unneeded compilation. This has to
do with how the compiler handles dependency tracking. For our part,
we avoid placing make style dependencies as rules upon the compilation
of a particular class file and leave this up to the Java compiler instead.
The --enable-maintainer-mode option to configure currently does very
little and shouldn't be used by ordinary develoeprs or users anyway.
|
