On 02/11/17 05:06, Tom Kent via Boost wrote:
After many hours of debugging, I got to the issue. It isn't a boost issue, Microsoft *did* break VS 2008 (msvc-9.0) when you install Visual Studio 2017!
I've detailed the bug here: https://connect.microsoft.com/VisualStudio/feedback/details/3121194
It only manifests itself when you try to set the visual studio environmental variables from a 32-bit shell (I ran my regression tests from a 32-bit python instance, which gives you a 32-bit shell the rest of the way down) and try to build 64-bit. The 32-bit version of the registry loses the *VALUE* for the key found by the command `reg query "HKLM\SOFTWARE\Microsoft SDKs\Windows" /v "CurrentInstallFolder"`.
I'm going to move my regression runs to using python-64 bit, so that should fix things.
Thanks Tom for taking the time debugging this.