[Scons-users] default toolchain in Scons breaking on windows
bill at baddogconsulting.com
Tue Feb 20 15:04:29 EST 2018
Note.. that should also reduce some startup time.
Especially if you're never using any of the builders without an
On Tue, Feb 20, 2018 at 2:34 PM, Jason Kenny <dragon512 at live.com> wrote:
> That worked.
> *From:* Scons-users <scons-users-bounces at scons.org> on behalf of Bill
> Deegan <bill at baddogconsulting.com>
> *Sent:* Tuesday, February 20, 2018 11:06 AM
> *To:* SCons users mailing list
> *Subject:* Re: [Scons-users] default toolchain in Scons breaking on
> DefaultEnvironment(tools=) at top of SConstruct.
> On Tue, Feb 20, 2018 at 11:52 AM, Jason Kenny <dragon512 at live.com> wrote:
> Hi Bill,
> I have a question for some advice on how to address an issue.
> As I am taking time again to fix up Parts. I have an issue open
> The issue here is that when starting SCons, logic to load the "default"
> environment happens before the SConstruct is read in. This on windows will
> try to load the "default" tool on windows which always tries to load MSVC.
> The tools in Parts I have do not have this issue, however, I have no way to
> tell SCons about this as the SConstruct is where I get imported. Honestly,
> there really is not any good way I know of to affect the load logic for the
> tools in SCons before it loads the SConsstruct.
> Do you have any thoughts on this?
> Scons-users mailing list
> Scons-users at scons.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Scons-users