[Scons-users] compiler detection
Kraus Philipp
philipp.kraus at flashpixx.de
Mon Oct 29 15:40:02 EDT 2012
Am 29.10.2012 um 18:21 schrieb Evan Driscoll:
> On 10/29/2012 11:42 AM, Philipp Kraus wrote:
>> But I have got on MinGW a "shell" problem, because I use 2 env.Command
>> lines, and this commands are always run on cmd.exe, but MinGW uses by
>> default /bin/sh
>> I try to setup env["SHELL"] = "/bin/sh" and the PATH variable in my env
>> object, but by the env.Command line I get always that /bin/sh is not
>> found (and the command
>> creates an error).
>
> 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). 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.
More information about the Scons-users
mailing list