This is how building for VS2017 works for me... about openssl HOT 4 OPEN

I just saw that my previous text looks a bit garbled, so this is an attempt to upload my version of setVSvars.bat as a text file here, dunno if this works:

setVSvars.bat.txt

from openssl.

Thanks @skuskusku. I've cleaned up the build scripts, added support for the 16299 SDK, fixed a couple of issues and pushed out an update. Please try it and I'll merge it into the WinRT branch.

from openssl.

Hello Mr, Khouzam,

It builds for all platforms with _WKITS10VER=10.0.15063 successfully and all tests are passed successfully as well. I will try in the next few days with 10.0.16299. Is this branch expected to work with the 10240 SDK as well or isn't it worth a try at all?

As a side note: One thing I noticed is that when building from the IDE, the library project files always seem to want recompilation after a successful build. So when attempting to debug one of the test apps, VS will always prompt you to build the libraries again before debugging. This, of course is only a minor annoyance, and I don't know if this ever worked. But in case you can identify this as a regression, maybe you know what needs to be done from memory.

Thanks again,

--
S

from openssl.

Hello Mr. Khouzam,

I can confirm that things work as well with the 16299 SDK, all configurations build and test successfully. I tried with the 10240 SDK as well but this failed with

1>.\ms\winrt.cpp : fatal error C1107: could not find assembly 'windows.foundation.foundationcontract.winmd': please specify the assembly search path using /AI or by setting the LIBPATH environment variable

With settings for the 10240 SDK, the LIBPATH environment variable is just not set. So if this SDK is intended to be supported, something has still to be done here.

Let me know if this is enough information for merging into the main trunk.

Greetings,

--
Stefan

from openssl.