Re: MSVC 2015 builds Failing After 2017 Support added

David Ostrovsky <d.ostrovsky -AT- gmx.de>
Wed, 22 Feb 2017 00:19:31 +0100

On Sun, 2017-02-19 at 20:53 +0000, Luke Benes wrote:

config_host.mk: 
export UCRTSDKDIR=C:/PROGRA~2/WI3CF2~1/10/
export UCRTVERSION=10.0.10240.0

Looking at the creation date of that folder, it matches the creation
 date of C:\Program Files (x86)\Microsoft Visual Studio 14.0.


Thanks again for the infos and apologize for the regression. It should
be fixed now for all supported compiler/SDK permutations in:[1].

* [1] https://gerrit.libreoffice.org/34528

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.