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
To build xtc’s classes,
junit.jar should be in the Java class path.
/Library/Java/Homeon Mac OS X.
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/classes.jaron Mac OS X. Only set this environment variable when using Jikes as the Java compiler.
~/xtc/classes:~/xtc/bin/junit.jar:~/xtc/bin/javabdd.jaron Unix systems.
:” for Unix.
:ext:user@machine:/home/pervasive/vault. Only set this environment variable if you have access to xtc’s CVS repository.
/usr/bin/ssh. Only set this environment variable if you have access to xtc’s CVS repository.
An example shell script for Unix (
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.jarcontains all classes necessary for running xtc.
rats-runtime.jarcontains only the classes necessary for running Rats!-generated parsers.
dist, which generates two zip files:
xtc-core.zipcontains xtc’s source code.
xtc-testsuite.zipcontains xtc’s regression tests.
stats, which prints JavaNCSS generated source code statistics.
check, which runs all regression tests.
javadoccomments. Though, we use two spaces as the unit of indentation (and no tab characters).