Instructions for using "Binary Releases"
These releases are in fact, full copies of the released code on
each OS. If you choose not to install the code development tools, you can still
run the executables.
- extract the both the external libraries and GLAST code from the archive files into
a single (top) directory, for sake of explicitness say '/home/richard/ground/'. A sub-directory structure will get created.
- Create an environment variable GLAST_EXT which points to where the extlib/
directory went (including the 'extlib'), eg /home/richard/ground/extlib.
- edit the application's setup file (.bat, .sh or .csh depending on your OS
and shell) and change the disk addresses to point to
the top directory you extracted the code into (eg find the setup file in
/home/richard/ground/pdrApp_v7r1/pdrApp/v7r1/cmt). This is a single global replace.
- run the setup file (from anywhere) and then the application from the executables directory
(eg /home/richard/ground/pdrApp_v7r1/pdrApp/v7r1/i386_linux22). On Windows,
you need to run these from a DOS prompt.
- extract both the the external libraries and GLAST code from the archive files into
a single (top) directory, for sake of explicitness say 'ground/'. A sub-directory structure will get created.
- Create an environment variable GLAST_EXT which points to where the extlib/
directory went (including the 'extlib'), eg /home/richard/ground/extlib.
- install cvs, ssh, CMT (and vcmt as needed) as per the general
instructions
- point your CMTPATH to the directories that were created. For pdrApp, these
will look like (eg) gaudi_v7, gismosys_v5r4, pdrApp_v7r1
- recreate the application's setup file in its cmt directory and off you go.
Last Modified: 11/21/2001 17:26