Re: MSVC 2015 builds Failing After 2017 Support added

David Ostrovsky <d.ostrovsky -AT- gmx.de>
Sun, 19 Feb 2017 20:35:30 +0100

On Sun, 2017-02-19 at 18:56 +0000, Luke Benes wrote:

 The default should be that whatever comes with the compiler should
be
 enough, and that installing any separate SDK should be optional.



Agreed, this is how MSVC 2015 worked before the 2017 patch.

 So, if your UCRTVERSION is 10.0.10240.0 (can you verify in
config_host.mk?)


I don't see the answer to my question above.

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.