<html><body><p><tt><font size="2">> From: vin <vinayashreeks18@gmail.com></font></tt><br><tt><font size="2">> To: openssl-users@openssl.org</font></tt><br><tt><font size="2">> Date: 05/10/2019 12:44 AM</font></tt><br><tt><font size="2">> Subject: Re: Issue in linking Openssl1.1.1b to application</font></tt><br><tt><font size="2">> Sent by: "openssl-users" <openssl-users-bounces@openssl.org></font></tt><br><tt><font size="2">> <br>> Hi Ken<br>> <br>> I am almost struck in registering the built dll to windows 7 32 bit machine.<br>> <br>> Can you provide me the details on which all openssl1.1.1b output lib files<br>> and output dll files that needs to be linked to any application while<br>> building in visual studio??</font></tt><br><br><tt><font size="2">With mingw, I specify this to the linker</font></tt><br><br><tt><font size="2">c:/program files/openssl/lib/mingw/libcrypto-1_1.a</font></tt><br><br><tt><font size="2">In Visual Studio,</font></tt><br><br><tt><font size="2">Linker - Input - Additional Dependencies: libcrypto32mdd.lib</font></tt><br><tt><font size="2">Linker - General - </font></tt><tt><font size="2">Additional Library Directory: c:\program files\openssl\lib\vc</font></tt><br><br><tt><font size="2">However, it sounded like you were linking correctly, but Windows could</font></tt><br><tt><font size="2">not find the dll at runtime. That points to a PATH issue.</font></tt><br><tt><font size="2"><br>> <br>> Or any steps needs to be added while building openssl1.1.1b,I am following<br>> the steps below<br>> Windows 32-bit<br>> 1. perl Configure VC-WIN32<br>> 2. nmake<br>> 3. nmake test<br>> 4. nmake install<br></font></tt><br><tt><font size="2">I don't build myself. I use Shining Light:</font></tt><br><br><a href="http://slproweb.com/products/Win32OpenSSL.html"><tt><font size="2">http://slproweb.com/products/Win32OpenSSL.html</font></tt></a><BR>
</body></html>