Re: MSVC 2015 builds Failing After 2017 Support added

slacka <lukebenes -AT- hotmail.com>
Sat, 18 Feb 2017 20:16:24 -0700 (MST)

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.

Context

MSVC 2015 builds Failing After 2017 Support added · Luke Benes
- Re: MSVC 2015 builds Failing After 2017 Support added · Kaganski Mike
  - Re: MSVC 2015 builds Failing After 2017 Support added · slacka
    - Re: MSVC 2015 builds Failing After 2017 Support added · Tor Lillqvist
      - Re: MSVC 2015 builds Failing After 2017 Support added · Luke Benes
        
        Re: MSVC 2015 builds Failing After 2017 Support added · David Ostrovsky
        
        Re: MSVC 2015 builds Failing After 2017 Support added · Luke Benes
        
        Re: MSVC 2015 builds Failing After 2017 Support added · David Ostrovsky
        Re: MSVC 2015 builds Failing After 2017 Support added · Stephan Bergmann
        
        Re: MSVC 2015 builds Failing After 2017 Support added · David Ostrovsky
        Re: MSVC 2015 builds Failing After 2017 Support added · Stephan Bergmann

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.