On Sat, Sep 6, 2014 at 8:41 AM, anatoly techtonik <[email protected]> wrote:
> >> complexity#002 - How default tools work? > >> SCons is somehow able to find default GCC or default MSVC without > >> env/PATH patch. SCons doesn't use $PATH to find MSVC, it uses the registry. That's the Microsoft-approved way to do it. > But when MSVC is unavailable on Windows, SCons > >> doesn't fallback to GCC even if GCC is in PATH. Why? > > > > Because the current "tool chain" logic doesn't support that. It's one of > > the major goals of my revamp to have fallback tools. See the wiki page. > > Dammit. I am trying to address **specific** simple points right > here right now, and you're trying to stop the process by switching > discussion from these specific point to some abstract "revamp" > idea on a wiki page that doesn't even have an address. > I already replied to your pull request idea for a MissingDefaultTool, which I think is a great stopgap. If you can implement that in such a way that a missing MSVC install avoids the empty $CC string problem, then we can hide the warning (as you suggest in the PR) and I think that will address the specific case Russel started this thread with. I would suggest implementing MissingDefaultTool in as simple a way as possible, minimizing refactoring, and targeting MSVC only for now. -- Gary
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
