VS2017 Support
dg2k opened this issue · 4 comments
When to expect updates for VS2017?
Could someone respond? My query from 29 days ago is still open.
Sorry, I have not had time to update the scripts yet. Let me look at what needs to be done.
@khouzam Thank you for the response.
I tried a quick customized fix to enable me to compile but very tricky - one challenge I noted is that VS2017 now uses private registry settings tucked away in App Package folder and things as not as straightforward as VS2015 or previous versions. Hence, VS path determination from registry is not that easy (unless it's possible to "Load Hive" of a private registry via script which I never attempted. It means the script needs to be revamped for VS2017 and steered away from it and leave it to MS expertise ;-)
Hope something comes up soon.
Hi @dg2k,
I've pushed a new branch with the VS2017 support: OpenSSL_1_0_2_WinRT-stable-vs2017
Please try it. There are a couple of things that need to be figured out, but it does work for VS2017 with the 15063 Windows 10 SDK.
Some things that have to be adjusted:
- Currently if you have VS2017, it will default to that for Windows 10.
- Some APIs that we were thunking were added back in the 15063 SDK, so I commented out our version, but that might mean that other SDKs are broken.
- Need to consolidate the scripts and pass the version of the SDK requested and version of VS. But that might be a longer term thing that we try to update to OpenSSL 1.1.0
Simply invoke ms\do_vsprojects15.bat to generate the VS2017 solution.