Difference between revisions of "GlueX Software Setup"
From GlueXWiki
(→Build Dependencies) |
|||
| Line 4: | Line 4: | ||
* If you re-build one of the following, you must also rebuild (in order): | * If you re-build one of the following, you must also rebuild (in order): | ||
| + | <pre> | ||
Xerces: HDDS, JANA, sim-recon | Xerces: HDDS, JANA, sim-recon | ||
ROOT: JANA, sim-recon | ROOT: JANA, sim-recon | ||
| Line 10: | Line 11: | ||
JANA: sim-recon | JANA: sim-recon | ||
EVIO: sim-recon | EVIO: sim-recon | ||
| + | </pre> | ||
== Environment == | == Environment == | ||
Revision as of 16:35, 17 July 2014
Contents
Software
Build Dependencies
- If you re-build one of the following, you must also rebuild (in order):
Xerces: HDDS, JANA, sim-recon ROOT: JANA, sim-recon CCDB: JANA, sim-recon HDDS: sim-recon JANA: sim-recon EVIO: sim-recon
Environment
- There should be three levels for the software environment: user-specific, release-specific, and base. For best-practice, environment variables should NEVER EVER (!!) be put in your .cshrc (or equivalent) file. This is because if you ever need to switch between environments (e.g. between a "data challenge" release and the latest trunk) it gets very messy and it's very easy to make a mistake. It's far safer (and cleaner) to keep everything separate.
User-Specific Environment Setup
- E.g. env_gluex_pmatt_2014_07_17
Release-Specific Environment Setup
- E.g. env_gluex_2014_06_30_rhel6
Base Environment
env_gluex_base
