From email:

At the moment we do

./configure

Set MAUS_ROOT_DIR (i.e. MAUS location) to pwd
Set MAUS_THIRD_PARTY (i.e. Geant4/ROOT/python/etc) to pwd

./configure ~/dir

Set MAUS_ROOT_DIR (i.e. MAUS location) to pwd
Set MAUS_THIRD_PARTY (i.e. Geant4/ROOT/python/etc) to '~/dir'

--

I propose an alternative set up where we have

./configure

Set MAUS_ROOT_DIR (i.e. MAUS location) to pwd
Set MAUS_THIRD_PARTY (i.e. Geant4/ROOT/python/etc) to pwd

./configure -r ~/maus_root -t ~/maus_third

Set MAUS_ROOT_DIR (i.e. MAUS location) to '~/maus_root'
Set MAUS_THIRD_PARTY (i.e. Geant4/ROOT/python/etc) to '~/maus_third'

Would that satisfy requirements?

Should also add (to be specific)

./configure -r ~/maus_root

Set MAUS_ROOT_DIR (i.e. MAUS location) to '~/maus_root'
Set MAUS_THIRD_PARTY (i.e. Geant4/ROOT/python/etc) to '~/maus_root'

./configure -t ~/maus_third

Set MAUS_ROOT_DIR (i.e. MAUS location) to pwd
Set MAUS_THIRD_PARTY (i.e. Geant4/ROOT/python/etc) to '~/maus_third'

Note that subsequent infrastructure assumes that third party stuff is in the right place within maus_third i.e. third party install directory is at

$MAUS_THIRD_PARTY/third_party/install/include
$MAUS_THIRD_PARTY/third_party/install/lib

etc...

Also this must write env.sh to pwd (which may not be $MAUS_ROOT_DIR)

Now in test...

Closed in r893