Great tool, however, I had to do some mods to the current build because the paths are not set correctly for the 10.0.14393.0 toolchain. At the end of the ms/setVSvars.bat file I had to do change the lines to have different values (the .0 at the end is missing, so is some other stuff 2.0.0.0 instead of 1.0.0.0):
`
:setEnv
call:setVar _VS14VC VisualStudio14VC
call:setVar _WKITS10 WindowsKits10.0
call:setVar _WKITS10VER WindowsKits10Version
set PATH=%_VS14VC\Bin%;%PATH%
set INCLUDE=%_VS14VC%\include;%_WKITS10%\Include\%_WKITS10VER%.0\um;%_WKITS10%\Include\%_WKITS10VER%.0\shared;%_WKITS10%\Include\%_WKITS10VER%.0\winrt;%_WKITS10%\Include\%_WKITS10VER%.0\ucrt;
set LIB=%_VS14VC%\lib\store\%_VCLibPlat%;%_WKITS10%\lib\%_WKITS10VER%.0\um\%_VCPlatform%;%_WKITS10%\Lib\%_WKITS10VER%.0\ucrt\%_VCPlatform%;
set LIBPATH=%_WKITS10%\UnionMetadata\Facade;%_VS14VC%\vcpackages;;%_WKITS10%\references\windows.foundation.foundationcontract\2.0.0.0\;;%_WKITS10%\references\windows.foundation.universalapicontract\2.0.0.0\
goto :eof
:end
`
one more thing, in the build.cmd file, I guess you should copy the ssl lib as well:
COPY out32\ssleay32.lib ..\build\libs\uwp\%%P || goto :error)
and it would be favorable if the includes end in the subfolder, otherwise no other program will find the includes due to the <openssl/blabla.h> convention.
Great tool, however, I had to do some mods to the current build because the paths are not set correctly for the 10.0.14393.0 toolchain. At the end of the ms/setVSvars.bat file I had to do change the lines to have different values (the .0 at the end is missing, so is some other stuff 2.0.0.0 instead of 1.0.0.0):
`
`
one more thing, in the build.cmd file, I guess you should copy the ssl lib as well:
COPY out32\ssleay32.lib ..\build\libs\uwp\%%P || goto :error)and it would be favorable if the includes end in the subfolder, otherwise no other program will find the includes due to the <openssl/blabla.h> convention.