Adapt to Windows SDK 10.0.15063
On a machine with MSVC 2013 and 2015 (but no 2017) installed, I installed "Windows Software Development Kit - Windows 10.0.15063.137" as available through <https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk> (in the hopes that it will provide a better fix for acbb7e32 "Work around clang-cl issue with MSVC's safeint.h for now"). That apparently removed various files from the C:\Program Files (x86)\Windows Kits\10\bin\ hierarchy, while it added files to a new C:\Program Files (x86)\Windows Kits\10\bin\10.0.15063.0\ hierarchy (and <https://developer.microsoft.com/en-US/windows/downloads/windows-10-sdk> mentions that in an "SDK Layout Changes: Side by Side install of tools and metadata" section). So return a new winsdkbinsubdir var from find_winsdk() to cover installations that use this new layout scheme. In b076e8f6 "Fix include and library paths for at least me", tml had hardcoded some 10.0.15063 -> 10.0.14393 mappings that are unhelpful at least in my scenario. I tried to keep those hacks in in a way that would still work for tml's scenario. The check for msiinfo.exe etc. had been broken since ecfabb66 "add support for Windows 8 SDK", but apparently in a way so that nobody noticed. The first # needed for msi packaging pathmunge "$WINDOWS_SDK_BINDIR_NO_ARCH/x86" "before" is indeed needed, as (at least some of) those tools are only available in the arm and x86 sub-dirs, not in the arm64 and x64 ones. (I'm not sure whether the two later pathmunges adding $WINDOWS_SDK_BINDIR_NO_ARCH/{x64,x86} are still relevant, though.) Change-Id: Ia403e4bde7b1abf7e2c9d9f084a05af2d1311617 Reviewed-on: https://gerrit.libreoffice.org/36455Tested-by:Jenkins <ci@libreoffice.org> Reviewed-by:
Stephan Bergmann <sbergman@redhat.com>
Showing
Please
register
or
sign in
to comment