First of all, we strongly suggest using Java 2. And you will
definitely require a version of GNU make. Wherever we use the command make, it is assumed
to refer to the GNU make executable..
cvs -d :pserver:anoncvs@www.omegahat.org:/home/anoncvs/src/omegahat loginIt will prompt for a password and you reply with
anonymousYou can then set the environment variable
CVSROOT
to
:pserver:anoncvs@www.omegahat.org:/home/anoncvs/src/omegahator specify it in each cvs command via the -d argument.
cvs -d :pserver:anoncvs@www.omegahat.org:/home/anoncvs/src/omegahat operationAlso, most cvs commands can augmented with a -z3, or some other suitable value to turn on compression. For those with slow connections, this might be useful.
org/ (to satisfy the
Java package mechanism).
mkdir org
cd org
cvs checkout omegahat
cd omegahat
setenv OMEGA_HOME `pwd` # or export OMEGA_HOME=`pwd`
It is probably a good idea to set the OMEGA_HOME
in your .login or shell initialization script.
Now, we get the individual modules. For example, the following command gets all of them. Remove entries from the list as you want.
cvs checkout Environment DataStructures Models Graphics Numerics Interfaces JTools S R LispStat SimulationAlternatively, you can use the rules in the GNUmakefile (having edited the configuration files, modules.nw, etc.)
make checkout(assuming make is a version of the GNU make utility.)
If you have alread checked out the different
modules, from within
the org/omegahat/
directory (i.e. OMEGA_HOME),
issue the command
cvs updateor, update individual modules, e.g.
cvs update ModelsNote that when you update, it is recommended that you compile all the classes again. You can do this easily with
make clean cleanJava make
To find out which modules will be compiled, issue the command
make listModulesin the top-level directory
$OMEGA_HOME/
If you want to change this list, edit the MODULES
file (or preferrably the modules.nw
file which will be automatically rebuilt).
OMEGA_HOME/Jars/
A complete list is given below.
Those jar files needed for the interpreter are:
Config directory. Issue the command
make. This builds the file local.config
amongst several others that are build by inclusion.
Now, you should edit this file, uncommenting settings that are
incorrect and editing the right hand side of the definition
to a value appropriate for your system.
The most likely variables you will have to set are
JAVA_HOME, identifying the directory containing the Java
distribution on your machine, JAVA2, indicating whether
you are using Java2 (set this to true if you are) and
WEB, providing the name of the executable for running notangle, the
noweb converter to source code. If notangle
is in your path, you need not doing anything.
For an explanation of the different variables, see Omegahat Configuration
Variables.
omegahat shell script. (You can of course
embed any of the classes in another application.) Having built the
class files, you should create the scripts. Move to the directory
$OMEGA_HOME/binmake(Alternatively, you can issue the command
gmake scripts from the
$OMEGA_HOME/omegahat
omegahat ScriptOMEGA_HOME
environment variable in their login/shell initialization scripts. One
can also add the directory $OMEGA_HOMEomegahat script can be invoked without a qualifying
directory name.
In order to make the installation available for other users, one may want to move the If one want
Environment/Parser/Parse
now rely on these in a few simple places.
The files that cause the problems are
Obtain this from the usual sources:
In theory, one can use a different Java compiler and JVM. We have experimented with guavac and jikes and kaffe and japhar. See JVM links.
If anyone succeeds in compiling and/or running a version on a different machine, or with different tools, please let us know. We will add this to the list of known working combinations.
local.config.