We used to keep the build environment setup in
envConfig/${PROTEUS_ARCH}.bash. Those files effectively included what we
now put in the hashstack PROLOGUE. At the moment we've sort of regressed on
the proteus side because we've got rid of envConfig, so we have to set up
the build environment manually or in the users .bashrc.  In the pbs script
above we were using the envConfig script to set up the runtime environment
on the compute nodes, which used to be needed because those module loads
for the build environments also set LD_LIBRARY_PATH.  My points are that 1)
the stuff in PROTEUS_ENV has not always been sufficient, though it may be
now and 2) We need to revisit the issue of how to set up a proteus
developer's environment.


On Fri, Feb 21, 2014 at 9:45 AM, Aron Ahmadia <notifications@github.com>wrote:

> In test/test_proteus_garnet.pbs:
>
> >  source /opt/modules/default/etc/modules.sh
> > -source ${PROTEUS}/envConfig/garnet.gnu.bash
> > +source ${PROTEUS}/proteus_env.sh
>
> Actually, I was just dumping the output of PROTEUS_ENV from the Makefile
> and that was sufficient. It's a few lines of code to create this file.
> ... <#144551fd8fdabe9b_>
> On Fri, Feb 21, 2014 at 10:43 AM, Chris Kees <notifications@github.com>wrote:
> In test/test_proteus_garnet.pbs: > source
> /opt/modules/default/etc/modules.sh > -source
> ${PROTEUS}/envConfig/garnet.gnu.bash > +source ${PROTEUS}/proteus_env.sh
> yeah, it would be nice to grab the PATH and PROLOGUE from hashstack and add
> prepend PROTEUS_PREFIX/bin and PROTEUS_PREFIX/lib to the
> PATH/LD_LIBRARY_PATH. -- Reply to this email directly or view it on GitHub<
> https://github.com/erdc-cm/proteus/pull/39/files#r9949398> .
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/erdc-cm/proteus/pull/39/files#r9949487>
> .
>