Installation Instructions

Martin Frank
frank@isi.edu

The list below assumes that you are on a PC and have to install everything from scratch. All software needed is freely available.

Instructions for Java Source Code

  1. Install the UNIX utilities on your NT-based PC (skip if you are running a UNIX variant in the first place!). Download from: http://www.cygwin.com
  2. Install Emacs for Windows from http://www.gnu.ai.mit.edu/software/emacs/emacs.html If we jointly work on the same source files, I suggest you also create a C:/usr/home or C:/cygwin/usr/home directory, download our source code indentation preferences JAR file to it, unzip it, and set your HOME environment variable to that location. Set the environment variable EMACS to e.g. "//c/Program/ Files/emacs-20.7" (without the quotes) so that you can say "make emacs" to invoke it from a shell and say "make tags" for M-x tags-search and M-x tags-query-replace support in Emacs.
  3. Download/install the Java Development Kit 1.4.1 or later from http://java.sun.com/products/jdk
  4. Set the environment variable JDK_HOME to the Java JDK directory (to the one that contains the lib and bin files), using a forward-slash PC syntax such as "C:/jdk1.4.1"
  5. If you actually want to share live sources with us (as opposed to just making a copy of the source code):
  6. Create a new directory and call it e.g. AllProjects (you get to name it)
  7. Set the environment variable DCE_HOME to the absolute path name to and including AllProjects - use forward-slash PC syntax such as "C:/Code/AllProjects". Under a Unix variant, set it to "/Code/AllProjects".
  8. Set the environment variable CLASSPATH_SEPARATOR to ";" if you run Windows and ":" if you run UNIX.

Instructions for LaTeX/Texinfo Documents

Some projects keep their documents in these formats. Typically, the generated output is checked into CVS so that you do not have to install the below if you just want to read the documentation. However, if you want to create or modify documents in these formats, install the following:
  1. Install MikTex from http://www.miktex.org. Recommend you choose the largest of the install sizes provided (even though the smallest will probably do if you are short on disk space).
  2. The MikTex installer will have added the MikTex bin directory in front of your Windows system path. However, this is not good enough because a cygwin shell will put its bin directory in front of that - which contains outdated and incompatible versions of some of the MikTex tools. Thus, remove the "C:\freeware\texmf\miktex\bin;" (or similar, depending where you installed MikTex) prefix from the PATH in the Windows Control Panel "System" Environment tab. Instead, put the following line (or similar, depending where you installed MikTex) at the very end of your ~/.bashrc file (without the double quotes): "export PATH=/cygdrive/c/freeware/texmf/miktex/bin:$PATH"
  3. Start a new Cygwin shell (type "echo $PATH" without the quotes to verify the MikTex bin directory is indded at teh front of your PATH now). You should now be able to say "make" in the documentation directories.

Instructions for Creating a New CVS Mnodule

  1. cd $DCE_HOME; cvs checkout CVSROOT; cd CVSROOT
  2. edit the "modules" file there
  3. cvs commit -m "whatever" modules
  4. telnet to tnt and login with your personal login and password
  5. say "rlogin tnt -l dceg_cvs" - it should not ask you for a password, say "cd cvs-master-link" and manually "mkdir" the directory of the new CVS module(s) you defined (for example, the "snap" module would be in the "systems" subdirectory per its definition in the modules file)
  6. log out twice so that you're back to your local machine
  7. WARNING: if you already have the directory that the step below will create, re-name it to make sure CVS doesn't delete its contents
  8. cd $DCE_HOME; cvs checkout yournewmodule, and it should create it on your local hard disk (make sure you don't have the -P option set on your cvs checkout, or it will not ever create the new directory as it is still empty)
  9. Now add content to the new directory and you can "cvs add" and "cvs commit" there as usual.

Instructions specific to CAMERA/SNAP/CACE/CARTE

The CAMERA software includes SNAP, the Marine Corps flight scheduling application.

Instructions specific to WebScripter

The WebScripter software includes the WebScripter report mechanism Java source code as well as the XML/XSL/RDF/DAML sources of the WebScripter Web site.

Instructions specific to MASTERMIND

The MASTERMIND software Adaptive Forms, the Plan Editor, and more.