[Scons-users] MSVC is broken for x86 builds on x64 hosts

[Joseph C. Brill]

Michael

 

Is it possible to include the environment id to the print statements that
you added?  Something similar to:  id(env).

 

This would confirm one of the following two things:

-          There is single environment that is corrupted prior to the second
initialization call sequence started from mslink.py

-          There are two or more environments that are likely being
initialized correctly.

 

As others have indicated, it appears that a second environment (possibly
without the msvc arguments or any arguments at all) is involved.

 

If a second environment is manifested it should be fairly straightforward to
detect and raise an exception.

 

If there is only a single environment it will likely be more involved.  

 

>From the pastebin, the sequence of calls to in setup the environment is
identical.  I'm guessing that it just so happens that mslink.py is the first
ms tool to initialize a new environment (or corrupted environment) and may
not be responsible for any errors.  Again, just a guess.

 

Joe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20190523/9c93d564/attachment.html>