Viper Installation Instructions

SOURCE, BINARY and DOCUMENTATION  DISTRIBUTION - viper.zip

Contents:

• Pre-Compiled Viper classes - viperbin.jar (JDK 1.2)
• Viper Source -  vipersrc.jar
• Associated test files, usage instructions and javadoc documentation.

VIPER INSTALLATION OPTIONS:

• It can be installed as a jar archive containing the precompiled classes.
• It can be built from "scratch" from its source code.

PREREQUISTES FOR USING PRE-COMPILED CLASSES:

The following software must be properly installed prior to the installation of Viper:

• Java 1.1 (or higher) - The Java compiler and runtime system.  http://www.javasoft.com
• JGL 3.1 - The Java Generic Library.   http://www.objectspace.com/jgl

INSTALLATION OF VIPER (all platforms):

Create a directory that will serve as the application's directory. Copy the jar archive (viper.jar) to that directory.
 

• Unpack the file. The file can be unpacked with java's jar utility - jar xvf viper.jar
• The following files and directories should be unpacked:

  META-INF/
  README
  VIPER.DOC
  index.html
  install.html
  docs/
  build.bat
  constraints.wrl
  run.html
  stdNodes.wrl
  testWrld.wrl
  viper
  viper.bat
  viperbin.jar
  vipersrc.jar

TO RUN THE BINARY DISTRIBUTION:
 

Update your CLASSPATH variable to include the full path to "viperbin.jar". META-INF isn't used and can be deleted. Under dos, "viper" can also be deleted, as well as the source jar file "vipersrc.jar".  Under unix, 'viper.bat' files can be deleted. See the README file for running viper.

PREREQUISTES FOR BUILDING FROM SOURCE CODE:

The following software must be properly installed prior to the installation of Viper.
 

• Java 1.1 (or higher) - The Java compiler and runtime system - http://www.javasoft.com
• JGL 3.1 - The Java Generic Library - http://www.objectspace.com/jgl
• JavaCC 0.7 - The Java Compiler Compiler.

UNPACKING THE SOURCE CODE (all platforms):

In the same directory in which viper.jar was unpacked, you will find the file named vipersrc.jar  The file can be unpacked with java's jar utility:

    jar xvf vipersrc.jar

This creates the subdirectory structure:  gov/nist/itl/sdct/viper that corresponds to the package name: gov.nist.itl.sdct.viper.   In order to
compile the source code in the viper directory, your classpath must include the path to the viper installation directory containing the "gov"
subdirectory.

BUILDING FROM SOURCE CODE WITHOUT MAKE:

Note: the following instructions were found not to work for Windows 95. Installation instructions for Windows 95/NT are given below.

After the source code has been unpacked, the application can be built  in the viper directory. Change directories to "gov/nist/itl/sdct/viper/parser" in unix or "gov\nist\itl\sdct\viper\parser" in dos. Then:

     javacc parser.jj

Change directories to "gov/nist/itl/sdct/viper" in unix or "gov\nist\itl\sdct\viper" in dos. Then:

     javac  Viper.java

See the README file for running viper.

BUILDING  FROM SOURCE CODE IN UNIX USING MAKE:
 

After the source code has been unpacked, the application can be built  in the viper directory. Change directories to "gov/nist/itl/sdct/viper". Then invoke "make" and everything should compile.

See the README file for running viper.

BUILDING FROM SOURCE CODE IN WINDOWS 95/NT USING build.bat:

After the source code has been unpacked, the application can be built by invoking "build.bat". "build.bat" has to be invoked from the directory where viper was unpacked, not in the viper directory, "gov\nist\itl\sdct\viper". After build completes change to the viper directory, "gov\nist\itl\sdct\viper".

See the README file for running viper.