MSVC 2015 builds Failing After 2017 Support added

[slacka]

Thanks for the work-around, but that doesn't really answer my question. 

To clarify, before support for MSVC 2017 was added, I did not need the Win
10 SDK. Even after, I do not need the Win 10 SDK to build with MSVC 2013.
Only MSVC 2015 has this new requirement.

Was this change intentional? If so, I'll update the wiki documentation to
mention this.



--
View this message in context: http://nabble.documentfoundation.org/MSVC-2015-s-broken-static-initializer-list-causing-build-failure-tp4202928p4208349.html
Sent from the Dev mailing list archive at Nabble.com.