[Scons-users] compiler detection

Evan Driscoll driscoll at cs.wisc.edu
Mon Oct 29 15:40:03 EDT 2012


On 10/29/2012 02:40 PM, Kraus Philipp wrote:

>

> Am 29.10.2012 um 18:21 schrieb Evan Driscoll:

>> Native Python/SCons knows nothing of MinGW paths; the /usr/bin/sh and

>> /c/blah paths are translated to Windows paths by the MinGW libraries.

>>

>> You need to set env["SHELL'] to whatever the physical location of sh.exe

>> is, e.g. env["SHELL"] = "c:/programs/mingw/bin/sh.exe" to make something up.

>

> The scons script is run from the MinGW shell (it is /bin/sh).


...as I said before, that doesn't matter.



> I have tried to setup the Windows

> path to the sh.exe and also the unix-styled path, in all cases the env.command stops with

> the error that the shell is not found.


Open CMD.exe and enter the Windows path to sh.exe. Does it run?

When you put in the Windows path, are you perhaps using
unescaped-backslashes (which are then escaping other things)? Is there
any chance you're overwriting env["SHELL"] with something else later?

What's the (Windows) path to sh.exe? What's the exact line you're using
to set env["SHELL"]?

Evan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 554 bytes
Desc: OpenPGP digital signature
Url : <http://four.pairlist.net/pipermail/scons-users/attachments/20121029/b0a0c0f7/attachment.pgp>


More information about the Scons-users mailing list