[Scons-users] Seeking help getting scons up on windows with MinGW

[M Busche]

I fear I've gone astray in my attempts to setup python, scons, and MinGW under windows.  Here's what I've done so far.  Please make me aware of any boneheaded steps I've taken (or failed to take), and thank you for your patience.


1. I've installed MinGW and the WINDOWS versions of python and scons using their respective windows installers.


2. After this installation, I was sort of expecting my windows PATH variable (which is inherited by MinGW) to be updated so that python.exe was in the PATH.  It was not.  After manually updating my windows PATH to include c:\Python27, I can now run python from the MinGW prompt:

    $ python --version
    Python 2.7.3


3.  It appears that the scons installer dropped a bunch of stuff in /c/Python27/Scripts:

    $ ls /c/Python27/Scripts
    scons-2.1.0.bat       scons-time.py   sconsign-2.1.0.py
    scons-2.1.0.py        scons-time.pyc  sconsign-2.1.0.pyc
    scons-2.1.0.pyc       scons-time.pyo  sconsign-2.1.0.pyo
    scons-2.1.0.pyo       scons.bat       sconsign.py
    scons-time-2.1.0.py   scons.py        sconsign.pyc
    scons-time-2.1.0.pyc  scons.pyc       sconsign.pyo
    scons-time-2.1.0.pyo  scons.pyo


Now I don't think I should be attempting to run scons.bat from a MinGW shell prompt.  So what should I be doing to run scons?  I suppose I can do this:

    $ python /c/Python27/Scripts/scons.py --version
    SCons by Steven Knight et al.:
            script: v2.1.0.r5357[MODIFIED], 2011/09/09 21:31:03, by bdeegan on ubuntu
            engine: v2.1.0.r5357[MODIFIED], 2011/09/09 21:31:03, by bdeegan on ubuntu
            engine path: ['c:\\Python27\\Lib\\site-packages\\scons-2.1.0\\SCons']
    Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 The SCons Foundation


Looks ok, but that's a bit cumbersome, yes?  I suppose I could attempt to write a small scons shell script to turn around and invoke the above.  Snooping around on my ubuntu box, I see scons there is indeed a shell script (and not a trivial one at all!)

OK, I think I'll stop there and let someone tell me what I'm doing wrong.

Thanks,
Matt