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

H. S. Teoh hsteoh at quickfur.ath.cx
Mon Jul 1 11:02:17 EDT 2013

This was originally posted to the D mailing list, but reposting here
upon Russel's suggestion.

I used to be able to run SCons directly by invoking
/path/to/bootstrap.py, but the latest version of SCons fails to find the
appropriate files and aborts upon startup. Upon closer inspection, I
found that it was making a wrong assumption about the path to said files
(it assumes cwd = SCons root when it's still in the user's cwd).

The attached patch fixes this problem for me.

Hope this helps. Thanks!


To err is human; to forgive is not our policy. -- Samuel Adler
-------------- next part --------------
diff -r f57afb0b72f5 bootstrap.py
--- a/bootstrap.py Wed May 15 12:50:05 2013 +0100
+++ b/bootstrap.py Sat Jun 29 10:13:45 2013 -0700
@@ -197,7 +197,7 @@

scons_py = os.path.join('src', 'script', 'scons.py')
- src_engine = os.path.join('src', 'engine')
+ src_engine = os.path.join(script_dir, 'src', 'engine')
MANIFEST_in = find(os.path.join(src_engine, 'MANIFEST.in'))

files = [ scons_py ] + [os.path.join(src_engine, x)

More information about the Scons-users mailing list