|
Installation guide: Higher level modules
Introduction
This guide explains how to build the CAVERNsoft modules using GNU configure
scripts. The QUANTA
distribution should be installed, before trying to build CAVERNsoft
modules. Use this guide if you have downloaded and installed QUANTA-x.x.tar.gz
(where x.x stands for the version number).
NOTE: If you have downloaded modules-2.0.tar.gz visit this page.
Table of Contents
1. System Requirements
2. Building and installing the CAVERNsoft
modules
3. Support
System Requirements
The modules of CAVERNsoft G2 were tested on the platforms listed below.
| Platform |
Version
|
| SGI Irix |
6.5 |
| Linux |
Red Hat 7.2 |
Building and installing the CAVERNsoft modules
1. Downloading the distribution into a working directory
Download the modules distribution to a working directory. Uncompress
and untar the distribution. Use the following commands:
gunzip modules_x.x.x.tar.gz
tar -xvf modules_x.x.x.tar.gz
2. Building the CAVERNsoft modules
a. Type
configure
This will run the configure script and will set up the makefiles for your platform automatically.
Type 'configure --help' to find out what options you can use with the configure script.
A very useful configure command would be:
'configure --with-quanta-inc-dir=/usr/local/include/QUANTA/include --with-cave-inc-dir=/usr/local/CAVE/include --with-cave-libs-dir=/usr/local/CAVE/lib --enable-bin-type=n32'
The --enable-bin-type option can be 32 (for Linux only), n32 (for Irix).
b. The table below lists the default compilers used to build the libraries.
| Platform |
Default
Compiler |
| SGI Irix |
CC |
| Linux |
g++ |
c. Type
make
This command will build the CAVERNsoft libraries as per
the option given with the configure command.
3. Demo programs
The demo programs are a set of sample programs located in the 'demos'
sub directory of the distribution. The demo programs exist in two directories
under the demos sub directory (coanim, limbo). A 'README'
file in each directory describes
the demo programs.
Configure builds the demo programs automatically during make.
Look into each directory and use the docs/README.html file to understand
how the demos should be run.
Support
Send problems, questions and feedback to: cavern@evl.uic.edu
|
