Windows install fails ('openssl/opensslv.h': No such file or directory)

[bridgem]

Installing on Windows 10 fails (powershell command). Using python 3.7, VC++ 14.0 installed.
How can you tell the installer where openssl is installed? It needs the include & lib locations.

creating build\temp.win32-3.7\Release\build\temp.win32-3.7\Release
C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\HostX86\x86\cl.exe /c /nologo /Ox /W3 /GL /DNDEBUG /MD -IC:\Lang\Python3\include -IC:\Lang\Python3\include "-IC:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.17763.0\cppwinrt" /Tcbuild\temp.win32-3.7\Release\_openssl.c /Fobuild\temp.win32-3.7\Release\build\temp.win32-3.7\Release\_openssl.obj
  _openssl.c
  build\temp.win32-3.7\Release\_openssl.c(493): fatal error C1083: Cannot open include file: 'openssl/opensslv.h': No such file or directory
  error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\BuildTools\\VC\\Tools\\MSVC\\14.16.27023\\bin\\HostX86\\x86\\cl.exe' failed with exit status 2

  ----------------------------------------
  Failed building wheel for cryptography

[bridgem]

Include error solved: I did the following before running the install command in powershell:

$env:LIBPATH="C:\utils\OpenSSL-win64\lib"
$env:INCLUDE="C:\utils\OpenSSL-win64\include"

However, and although the libpath seems to be picked up, I still get a linking error with over 1,000 unresolved symbols:

    C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\bin\HostX86\x86\link.exe /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:C:\Lang\Python3\Libs /LIBPATH:c:\users\mbridge\lib\oracle-cli\libs /LIBPATH:c:\users\mbridge\lib\oracle-cli\PCbuild\win32 "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Tools\MSVC\14.16.27023\lib\x86" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17763.0\ucrt\x86" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17763.0\um\x86" /LIBPATH:C:\utils\OpenSSL-win64\lib libssl.lib libcrypto.lib advapi32.lib crypt32.lib gdi32.lib user32.lib ws2_32.lib /EXPORT:PyInit__openssl build\temp.win32-3.7\Release\build\temp.win32-3.7\Release\_openssl.obj /OUT:build\lib.win32-3.7\cryptography\hazmat\bindings\_openssl.cp37-win32.pyd /IMPLIB:build\temp.win32-3.7\Release\build\temp.win32-3.7\Release\_openssl.cp37-win32.lib /NXCOMPAT /DYNAMICBASE
       Creating library build\temp.win32-3.7\Release\build\temp.win32-3.7\Release\_openssl.cp37-win32.lib and object build\temp.win32-3.7\Release\build\temp.win32-3.7\Release\_openssl.cp37-win32.exp
    _openssl.obj : error LNK2001: unresolved external symbol _BIO_method_type
    _openssl.obj : error LNK2001: unresolved external symbol _BN_mul
    _openssl.obj : error LNK2001: unresolved external symbol _BN_nnmod
    _openssl.obj : error LNK2001: unresolved external symbol _DH_generate_key
    _openssl.obj : error LNK2001: unresolved external symbol _DH_check_pub_key
    _openssl.obj : error LNK2001: unresolved external symbol _d2i_RSAPublicKey_bio
...

[wajiii]

I also had a "File Not Found" issue with "opensslv.h", but in completely different context, MacOS Sierra (10.12.6). Sharing my experience here in case it can help anyone in the future:
Turned out my problem was an openssl installation included in another third-party tool (Octave), as I discovered via which openssl Grew suspicious when openssl version returned different info than brew info openssl. Wiped that app out entirely (though I could have just removed it from my PATH; I was just irritatwed with it), then ensured the Homebrew-managed openssh was the latest available and in my PATH (i.e., added /usr/local/openssh/bin to PATH).
Et voila, OCI CLI installation success! :D

[paul-hummel-oracle]

@wajiii, thanks for the tips regarding openssl.

We are also experimenting with upgrading package versions to overcome issues on windows 10 + python 3.7.

[paul-hummel-oracle]

With the release of https://github.com/oracle/oci-cli/releases/tag/v2.4.42, we upgraded third party module versions for requests, cx_Oracle, pyOpenSSL, and cryptography. This should resolve installation issues for Python 3.7 on Windows.