[Scons-dev] [Fwd: [Scons-users] [patch] SCons fails to run in standalone mode]

[Managan, Rob]

Hi Dirk,

In that revision this is what I see in README.rst

$ setenv MYSCONS=`pwd`/src
$ setenv SCONS_LIB_DIR=$MYSCONS/engine
$ python $MYSCONS/script/scons.py [arguments]


For cshell you don't want the "=" in the setenv statement. (of course I am
assuming any spaces in the directory names are handled appropriately)
I also find I don't need to use the third line. I just use "scons Š"

For a bash shell then the equal sign is correct but you need to change
setenv to export.

That is what I was trying to convey in the first email.

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
Rob Managan                             email managan at llnl.gov
LLNL                                             phone: 925-423-0903
P.O. Box 808, L-095                   FAX:   925-422-3389
Livermore, CA  94551-0808





On 7/8/13 9:04 AM, "Dirk Bächle" <tshortik at gmx.de> wrote:


>Hi Rob,

>

>On 08.07.2013 16:55, Managan, Rob wrote:

>> Does anyone else use the method of setting the environment variable

>> SCONS_LIB_DIR as mentioned in the README.rst? I should point out that

>>the

>> syntax is messed up there.

>>

>> When testing stuff myself I just use, in the top level of the checked

>>out

>> scons, for shell or tcshell

>>

>> [...]

>> or in bash

>>

>> export MYSCONS=`pwd`/src

>> export SCONS_LIB_DIR=$MYSCONS/engine

>

>this is what I use too, but I fail to see how this is different from the

>descriptions in the README.rst.

>

>Which version are you referring to? I'm looking at revision

>"0c9c8aff8f46"...

>

>Regards,

>

>Dirk

>

>_______________________________________________

>Scons-dev mailing list

>Scons-dev at scons.org

>http://two.pairlist.net/mailman/listinfo/scons-dev