| Configuration files outside gconfig directory [message #7531] |
Thu, 13 November 2008 15:20  |
Mohammad Al-Turany
Messages: 518
Registered: April 2004
Location: GSI, Germany
|
first-grade participant |
From: *gsi.de
|
|
Hi,
As discussed today in the software meeting, I modify the framework to check for the environmental variable CONFIG_DIR, if this is defined (i.e export CONFIG_DIR=/yourpath) the framework will look for the configuration files (g3Config, g4Config, etc..) in this directory if not found the default one will be used and this is done for the single files, i.e. you can define your CONFIG_DIR to a directory which only contains the g3Config.C, then this file is taken from there and all other files (g3Libs, etc) will be taken from the default one.
This is true for all configuration files and decay configuration files, except for the SetCuts.C because it is called from the g3Config.C (and/or g4Config.C , flConfig.C) So in case you use your own directory for the gXConfig files you have to call the SetCuts.C yourself.
At the moment these changes are in fairbase/base/trunk, so to test this please go to your $VMCWORKDIR/base and call:
svn switch https://subversion.gsi.de/fairroot/fairbase/trunk/base .
then recompile.
As soon as many people test this I will move it to the release branch in fairbase
regards
Mohammad
|
|
|
|
GSI Forum
Search
Help
Members
Login
Home
