We use the Java Standard Edition version 5 or higher and several Unix command line tools, including GNU make, find (either the GNU or BSD version will do), bison, cvs, Info-ZIP, expect, and DejaGnu. Note that all these programs must be part of your local path.
xtc also includes several shell scripts, which may assume features unique to bash.
A complete development installation also uses:
All these tools need to be installed in the bin
directory:
JFlex.jar for JFlex,javabdd.jar for JavaBDD,junit.jar for JUnit,ccl.jar, javacc.jar, javancss.jar
and jhbasic.jar for JavaNCSSTo build xtc’s classes, javabdd.jar
and junit.jar should be in the Java class path.
srcclassesdocjavadoc.binglrdataJAVA_HOME/Library/Java/Home on Mac OS X.JAVA_RUNTIME/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/classes.jar
on Mac OS X. Only set this environment variable when using
Jikes
as the Java compiler.JAVA_DEV_ROOT~/xtc on Unix.CLASSPATH~/xtc/classes:~/xtc/bin/junit.jar:~/xtc/bin/javabdd.jar
on Unix systems.PATH_SEP:” for Unix.CVSROOT:ext:user@machine:/home/pervasive/vault. Only set this
environment variable if you have access to xtc’s CVS repository.CVS_RSH/usr/bin/ssh. Only set this environment variable if
you have access to xtc’s CVS repository.An example shell script for Unix (setup.sh) is
contained in this directory.
The following make targets are supported:
configure, which configures the local system’s
C limits and types.classes, which is the default and builds all
classes.parsers, which builds all parsers.doc, which builds embedded Javadoc
documentation.clobber, which removes all classes, Javadoc
documentation, jar files, and source distribution zip files.clobber-parsers, which removes the source code for
all parsers.jars, which builds the xtc jar files:
xtc.jar contains all classes necessary for running
xtc.rats-runtime.jar contains only the classes necessary
for running Rats!-generated parsers.dist, which generates two zip
files:
xtc-core.zip contains xtc’s source code.
xtc-testsuite.zip contains xtc’s regression
tests.stats, which prints JavaNCSS generated source code
statistics.check, which runs all regression tests.javadoc comments. Though, we use two spaces
as the unit of indentation (and no tab characters).