Dirk,
On Sun, 2013-07-21 at 23:53 +0200, Dirk Bächle wrote:
[…]
I pushed a new pull request (#83) a few minutes ago. Looks like my
bootstrap folder wasn't as clean as it should've been, when I tested
the previous version. Sorry...
Looks like it is fixed now, thanks for all the documentation
Hi there,
On 20.07.2013 10:24, Russel Winder wrote:
On Fri, 2013-07-19 at 19:56 -0400, Gary Oberbrunner wrote:
[…]
OK, sorry that took so long. Merged. Hope that helps.
Thanks for picking up on this. Sadly, I get:
| python /home/Checkouts/Mercurial/SCons/bootstrap.py
/usr/bin/python
On Fri, 2013-07-19 at 19:56 -0400, Gary Oberbrunner wrote:
[…]
OK, sorry that took so long. Merged. Hope that helps.
Thanks for picking up on this. Sadly, I get:
| python /home/Checkouts/Mercurial/SCons/bootstrap.py
/usr/bin/python
On Sun, 2013-07-14 at 20:57 -0400, Gary Oberbrunner wrote:
I'm still here -- just working 24/7 at my day job -- soon Ill be back to
SConsing I think it's important that bootstrap.py be useful to run
scons directly out of its repo checkout. I use it like that. Haven't been
following the
Hi Gary,
On 15.07.2013 02:57, Gary Oberbrunner wrote:
I'm still here -- just working 24/7 at my day job -- soon Ill be back
to SConsing I think it's important that bootstrap.py be useful to
run scons directly out of its repo checkout. I use it like that.
Haven't been following the
On 13.07.2013 16:53, Russel Winder wrote:
On Tue, 2013-07-09 at 09:17 +0200, Dirk Bächle wrote:
[…]
In my view, bootstrap.py is more for creating the build packages. It can
also copy together a local working copy (the bootstrap folder), which
is fine for most cases when you simply want to start
I'm still here -- just working 24/7 at my day job -- soon Ill be back to
SConsing I think it's important that bootstrap.py be useful to run
scons directly out of its repo checkout. I use it like that. Haven't been
following the discussion closely but breaking that would not make me happy.
On Tue, 2013-07-09 at 09:17 +0200, Dirk Bächle wrote:
[…]
In my view, bootstrap.py is more for creating the build packages. It can
also copy together a local working copy (the bootstrap folder), which
is fine for most cases when you simply want to start SCons without fully
installing it.
On 09.07.2013 00:53, Russel Winder wrote:
On Mon, 2013-07-08 at 20:18 +0200, Dirk Bächle wrote:
On 08.07.2013 18:32, Managan, Rob wrote:
[...]
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.
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
setenv MYSCONS `pwd`/src
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
On 08.07.2013 18:32, Managan, Rob wrote:
[...]
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.
Ahhh, okay. I got it now.
Maybe we should take some action about this. Instead of all this long
Switching this to the Dev list. Has anyone fixed this bootstrap.py issue
already?
Forwarded Message
From: H. S. Teoh hst...@quickfur.ath.cx
Reply-to: SCons users mailing list scons-us...@scons.org
To: SCons users mailing list us...@scons.tigris.org
Subject: [Scons-users]
13 matches
Mail list logo
