Linux Installation (Developers): Install GLAST Software and External Libraries
The following procedure assumes that you have created the directories where you want the software to be installed in accordance with the recommended directory structure. To download and install the binaries for a particular checkout package and its corresponding external libraries: Decide which checkout package you wish to install GlastRelease, EngineeringModel, or ScienceTools - and the version of the package. If necessary, refer to the Release Manager to determine the release status of a version. Then decide whether or not to download External Libraries. To download, or not to download. If you are located at SLAC, you may want to link to SLAC Public's external libraries instead of downloading them to your machine. You can do this by setting up your .cshrc file. (See Modify Your SLAC Public Environment.) If you are working offsite, you should download the external libraries to your local machine. If you download the External Libraries and have not already done so, create a GLAST_EXT environment variable. This variable points to the directory containing the external libraries; for example:
GUI Installer. Click on Launch Installer Now! and follow the instructions on the GUI for installing both the release and the external libraries for the release. Note: If you decided not to download External Libraries, be sure to deselect them. If you experience problems, refer to: Glast Software Installer. Note: If you are a Linux user and prefer using a command line installer instead of a GUI, see Linux Command Line Installer. Once the installer is completed, you will have a number of directories installed in your instDir directory. One of those directories is called "bin". This directory contains the scripts used to run any of the applications available within your new binary distribution. For example, if you checked out GlastRelease and wish to run Gleam, you would: /fullPath/to/GlastInstall/bin/Gleam where an optional input parameter would be a jobOptions file; otherwise, a default jobOptions file will be used. Related TopicsAlso See:
|