GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » General » Why is there a hardcoded $PATH in config.sh?
Re: Why is there a hardcoded $PATH in config.sh? [message #15180 is a reply to message #15175] Mon, 12 August 2013 10:01 Go to previous messageGo to previous message
Andreas Herten is currently offline  Andreas Herten
Messages: 25
Registered: October 2011
Location: Jülich
continuous participant

From: *ikp.kfa-juelich.de
Hey Florian,

Ok, debugging experience is a very good reason for doing it this way. I accept Wink. And will think about modifying my own config.sh.


Just for curiosity, another question:
Wouldn't the way I suggested defining $PATH in the previous answer also solve any wrongly set variable? Prepending the PandaRoot-specific paths like
export PATH="$SIMPATH/bin:OTHERPATHS/:$PATH"

For ROOT / GEANT executables would then be searched first in the PandaRoot directories.

(PandaRoot version switching and $PATH lengthening would be a problem. That's true. There would be a script needed to strip the old PandaRoot/bin directory out of $PATH before adding it again (maybe based on the previous $SIMPATH value)...)

See you,
-Andreas
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: pbarpSystem
Next Topic: Subversion HOWTO
Goto Forum:
  


Current Time: Thu Apr 25 16:02:05 CEST 2024

Total time taken to generate the page: 0.01021 seconds