-- MichaeReese - 21 Jul 2013

In all of the following cases: If you do a local installation (inside a user folder) make sure that the environment variables for the compiler and runtime system are set. These point to include and library folders. In case you install libraries to your home folder (--prefix=$HOME), these environment variables are:

export LD_LIBRARY_PATH="$HOME/lib:$LD_LIBRARY_PATH";
export LIBRARY_PATH="$HOME/lib:$LIBRARY_PATH";
export LD_RUN_PATH="$HOME/lib:$LD_RUN_PATH";
export CPATH="$HOME/include:$CPATH";
export C_INCLUDE_PATH="$HOME/include:$C_INCLUDE_PATH";
export CPLUS_INCLUDE_PATH="$HOME/include:$CPLUS_INCLUDE_PATH";
export OBJC_INCLUDE_PATH="$HOME/include:$OBJC_INCLUDE_PATH";
export PKG_CONFIG_PATH="$HOME/lib/pkgconfig:$PKG_CONFIG_PATH";

First installation on GSI machines:

• ./autogen.sh --prefix=$HOME
• make install

First installation on not-GSI machines:

• make sure that you have the GSI event API installed. Get it here http://www-win.gsi.de/lea/eventapi.htm. Assuming that you have build this library in /home/me/eventapiV50
• ./autogen.sh --prefix=$HOME --with-gsievt-lib-path=/home/me/eventapiV50  --with-gsievt-include-path=/home/me/eventapiV5
• make install

Updating the package on GSI machines:

• git pull origin master
• make install

After typing make install, the program preplay will be installed in the $prefix/bin folder. The plugin libraries will be installed to $prefix/lib$. You can try to execute the preplay program to check if the system is working. Using other programs together with prespec is described separately

• GoFourUsage
• FairyUsage