On Sat, Sep 6, 2014 at 12:08 PM, Russel Winder <[email protected]> wrote:
> There appears to be a fundamental problem with SCons tests on Windows, > but this just maybe due to me using Windwoes for the first time in well > over 22 years. > > I install a compiler, well two actually, MinGW and DMD, both to their > preferred installations. Both are usable from cmd.exe. However SCons > does not find either of them. This would imply that SCons is ignoring > the %PATH% at the system level. > > Is this the case, or am I missing something. > It is the case. I think it's not right. If a tool is installed in its preferred location, SCons should find it, on whatever OS. (This is part of what Anatoly was mentioning before, but solving this wouldn't solve all of that problem.) It is tricky though, because SCons tools shouldn't muck with env['ENV']['PATH'] too much; otherwise adding a tool may change the result of a build. Some tools just put the whole path to the tool executable in as the value of, say, $CC. But that of course makes the generated compile lines look ugly. For MinGW in particular it might be dangerous to add its bin dir to env['ENV']['PATH'] because I think MinGW puts all kinds of Unixy tools in that bin dir, which (as William points out) would make builds less reproducible. -- Gary
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
