Date: prev next · Thread: first prev next last
2017 Archives by date, by thread · List index


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.


So it seems that even if you do not install the win 10 SDK component, the MSVC 2015 installer will 
still create the "Windows Kits" folder and install some files.


When the Win 10 SDK is not installed most of folders are nearly empty. For example the  
"bin\x86\ucrt" only contains 1 file, ucrtbased.dll. The entire "bin" tree is only a few meg vs ~2 
GB with a SDK installed. The only notable exception is the "Lib" folder which contains nearly 1 GB 
of data vs 2GB with the SDK installed.


Is there anything else I can provide? Would you like a full directory listing with and without the 
win 10 SDK installed?

________________________________
From: David Ostrovsky <d.ostrovsky@gmx.de>
Sent: Sunday, February 19, 2017 11:35 AM
To: Luke Benes
Cc: libreoffice-dev
Subject: Re: MSVC 2015 builds Failing After 2017 Support added

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


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.