<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi,<br>
<br>
On 2/19/2017 12:34 PM, David Ostrovsky wrote:<br>
</div>
<blockquote cite="mid:1487496885.16634.14.camel@gmx.de" type="cite">
<pre wrap="">Hm.., what was changed since MSVC 2017 support, is that we are passing
toolset version, see commit message of the change you pointed to, and
particularly this line in external packages make files:
$(if $(filter
$(UCRTVERSION),),,/p:WindowsTargetPlatformVersion=$(UCRTVERSION)) \
e.g.
<a class="moz-txt-link-freetext" href="https://cgit.freedesktop.org/libreoffice/core/diff/external/lcms2/Exter">https://cgit.freedesktop.org/libreoffice/core/diff/external/lcms2/Exter</a>
nalProject_lcms2.mk?id=b862cbdd345ec57c2595629ded6a3969e1e65d56
So, if your UCRTVERSION is 10.0.10240.0 (can you verify in
config_host.mk?), then the corresponding msbuild toolset must be
installed. Looks like you have only partially installed SDK 10 on your
machine, so you are on your own.
As explained in the commit message, that was needed to force msbuild to
use non default toolset (fro SDK 10) when no default one (SDK 8) is
installed on the system.</pre>
</blockquote>
<br>
Possibly offtopic here, but shouldn't we explicitly use v140_xp toolset with VS 2015 *until* there's a need to explicitly drop XP? Answering to possible Tor's reaction ;-) , I want to clarify that personally I am all for dropping XP at the very moment we would
need a single OS/compiler/... feature that we cannot have with it, but not earlier.<br>
<br>
<div class="moz-signature">-- <br>
Best regards,<br>
Mike Kaganski</div>
<span class="st4cursor"></span>
</body>
</html>