chicken and egg problem re-arises with RCDB

  • setup scripts want environment script
  • RCDB may not be installed yet
  • made build_scripts local versions, rcdb.csh and rcdb.sh in analogy to ccdb.
  • not pretty, but works
  • tagged a new version of build_scripts, version 1.10 that has this change among others

 

Advertisements

have build scripts use native ccdb set-up[?]

  • can’t do setup if ccdb not there
  • setup will fail if ccdb is not there, even for use
  • green field problem:
    • gluex install could download and unpack ccdb first, perhaps even build
      • take a peek at the makefile, see if this is possible
      • not easy to grab ccdb in the middle of environment setup
  • copy scripts from ccdb, check consistency?
    • would give false inconsistencies
  • Just do the copy, do not check consistency
    • problem with where script resides?
  • need a check that the environment set-up is the same between master branch of both
  • it’s a can of worms, leave things alone for now

 

“use a build” documentation

Default version of sim-recon:

source /group/halld/Software/scripts/build_scripts/gluex_env_jlab.(c)sh

Custom version of sim-recon:

Method 1

1) define HALLD_HOME and BMS_OSNAME
2) source $HALLD_HOME/$BMS_OSNAME/setenv.(c)sh

Method 2

1) define GLUEX_TOP, BUILD_SCRIPTS
2) identify a version.xml, /path/to/version.xml
3) source $BUILD_SCRIPTS/gluex_env_version.(c)sh /path/to/version.xml

Method 2′ (private version of sim-recon)

1) define GLUEX_TOP, BUILD_SCRIPTS
2) identify a version.xml, /path/to/version.xml
3) eval `$BUILD_SCRIPTS/version.pl $version_file`
4) setenv HALLD_HOME /path/to/sim-recon (or export HALLD_HOME=/path/to/sim-recon)
5) source $BUILD_SCRIPTS/gluex_env.(c)sh