Difference between revisions of "HOWTO use a pre-built release"

From GlueXWiki
Jump to: navigation, search
m (Find a compatible version)
Line 3: Line 3:
 
=Find a compatible version=
 
=Find a compatible version=
  
First determine your identifying tag. The identifying tag contains the operating system, the architecture, and the version of gcc you are using. To do this get a version of the script osrelease.pl and execute it. For example:
+
First determine your identifying tag. The identifying tag contains the operating system, the architecture, and the version of gcc you are using. To do this get a version of the script <code>osrelease.pl</code> and execute it. For example:
  
 
  svn co https://halldsvn.jlab.org/repos/trunk/scripts/build_scripts
 
  svn co https://halldsvn.jlab.org/repos/trunk/scripts/build_scripts
Line 15: Line 15:
 
  Linux_Fedora12-i686-gcc4.4.3
 
  Linux_Fedora12-i686-gcc4.4.3
  
On the JLab CUE:
+
or if you are on the JLab CUE:
  
 
  > /group/halld/Software/scripts/build_scripts/osrelease.pl
 
  > /group/halld/Software/scripts/build_scripts/osrelease.pl

Revision as of 11:42, 30 March 2010

If you have access to a pre-built version of the GlueX, you can use it without having to check out and build the entire set of sources.

Find a compatible version

First determine your identifying tag. The identifying tag contains the operating system, the architecture, and the version of gcc you are using. To do this get a version of the script osrelease.pl and execute it. For example:

svn co https://halldsvn.jlab.org/repos/trunk/scripts/build_scripts
A    build_scripts/clhep_env.csh
...
A    build_scripts/osrelease.pl
...
A    build_scripts/Makefile_cernlib
 U   build_scripts
> build_scripts/osrelease.pl
Linux_Fedora12-i686-gcc4.4.3

or if you are on the JLab CUE:

> /group/halld/Software/scripts/build_scripts/osrelease.pl
Linux_RHEL5-i686-gcc4.1.2

This tells you the identifying tag for the build you want (in the last case Linux_RHEL5-i686-gcc4.1.2). If the build in question is built for your machine, it will contain a directory with this name in the bin and lib directories.

Set your HALLD environment variables

  1. Set HALLD_HOME to point to the Hall D root directory (the one that contains src, lib, bin, and include).
  2. Set HALLD_MY to a directory of your choice, one for which you have write privileges.