Issue in linking Openssl1.1.1b to application

classic Classic list List threaded Threaded
6 messages Options
vin
Reply | Threaded
Open this post in threaded view
|

Issue in linking Openssl1.1.1b to application

vin
Hi

I was using an application with openssl0.9.8k .The procedure i used to link
openssl to my application using visual studio -2008 was after building
openssl i was linking libeay32.lib and ssleay32.lib to my application and
including header files from include folder.

Now with openssl1.1.1b ,after building openssl I am linking openssl.lib
,libcrypto.lib and libssl.lib to my application and including header
files.Building application using visual studio 2008 .And when i try to
register that built dll in windows 7 32 bit machine ,its giving error as
"RegSvr32 : The module XXX.dll failed to load.  Make sure the binary is
stored at the specified path or debug it to check for problems with the
binary or dependent .DLL files.
"  

Can anyone please tell me whether the library linking is enough or any dll
linking needs to be done??
Any step i am missing please let me know?

Thanks in advance



--
Sent from: http://openssl.6102.n7.nabble.com/OpenSSL-User-f3.html
Reply | Threaded
Open this post in threaded view
|

Re: Issue in linking Openssl1.1.1b to application

Ken Goldman-2
On 5/9/2019 10:03 AM, vin wrote:

> Hi
>
> I was using an application with openssl0.9.8k .The procedure i used to link
> openssl to my application using visual studio -2008 was after building
> openssl i was linking libeay32.lib and ssleay32.lib to my application and
> including header files from include folder.
>
> Now with openssl1.1.1b ,after building openssl I am linking openssl.lib
> ,libcrypto.lib and libssl.lib to my application and including header
> files.Building application using visual studio 2008 .And when i try to
> register that built dll in windows 7 32 bit machine ,its giving error as
> "RegSvr32 : The module XXX.dll failed to load.  Make sure the binary is
> stored at the specified path or debug it to check for problems with the
> binary or dependent .DLL files.
> "
>
> Can anyone please tell me whether the library linking is enough or any dll
> linking needs to be done??
> Any step i am missing please let me know?

I believe that you have to set the path to the dll in your PATH
environment variable.  There may be some default directories, but
setting the path should work.


vin
Reply | Threaded
Open this post in threaded view
|

Re: Issue in linking Openssl1.1.1b to application

vin
Hi Ken

Thanks for the reply.If I am not wrong ,You are asking me to set the path of
the dll in set path environment variable in testing machine (windows 7 32
bit) right??

But the issue is if same dll built with openssl0.9.8k is registering
properly in same test machine.

After replacing openssl libraries by openssl1.1.1b I am facing this issue.So
I guess building dll using visual studio 2008 is missing some steps .

Can you please help me further??



--
Sent from: http://openssl.6102.n7.nabble.com/OpenSSL-User-f3.html
Reply | Threaded
Open this post in threaded view
|

Re: Issue in linking Openssl1.1.1b to application

Ken Goldman-2

> From: vin <[hidden email]>
> To: [hidden email]
> Date: 05/09/2019 01:24 PM
> Subject: Re: Issue in linking Openssl1.1.1b to application
> Sent by: "openssl-users" <[hidden email]>
>
> Hi Ken
>
> Thanks for the reply.If I am not wrong ,You are asking me to set the path of
> the dll in set path environment variable in testing machine (windows 7 32
> bit) right??


Right.

In the PATH environment variable.

>
> But the issue is if same dll built with openssl0.9.8k is registering
> properly in same test machine.


If 098 used the Shining Light installer, I recall that there was/is an option to
install the dlls in the system area or not.  Perhaps you installed 098 in the
system area but not 111.

> After replacing openssl libraries by openssl1.1.1b I am facing this issue.So
> I guess building dll using visual studio 2008 is missing some steps .


Oh, wait!!!  I didn't notice that you're building openssl yourself.  I've
always used Shining Light.  So it could be a problem in the way they're
being build.

> Can you please help me further??

Sure.  I have 1.1 working with Visual Studio, although I still can't get
1.1 64-bit working with mingw.

vin
Reply | Threaded
Open this post in threaded view
|

Re: Issue in linking Openssl1.1.1b to application

vin
This post was updated on .
Hi Ken

I am almost struck in registering the built dll to windows 7 32 bit machine.
 
Can you provide me the details on which all openssl1.1.1b output lib files
and output dll files that needs to be linked to any application while
building in visual studio??

Or any steps needs to be added while building openssl1.1.1b,I am following
the steps below
Windows 32-bit
        1. perl Configure VC-WIN32
        2. nmake
        3. nmake test
        4. nmake install


Also I have checked built dll with http://www.dependencywalker.com/ application.This is the application which will show dll dependancies of any file.
For dll linked with openssl1.1.1b it is showing error as LIBCRYPTO-1_1.DLL not found and LIBSSL-1_1.DLL not found.
For dll linked with openssl0.9.8k the above 2 errors are not shown when tested in dependancy walker.

Can anyone help me in this?
--
Sent from: http://openssl.6102.n7.nabble.com/OpenSSL-User-f3.html
Reply | Threaded
Open this post in threaded view
|

Re: Issue in linking Openssl1.1.1b to application

Ken Goldman-2

> From: vin <[hidden email]>
> To: [hidden email]
> Date: 05/10/2019 12:44 AM
> Subject: Re: Issue in linking Openssl1.1.1b to application
> Sent by: "openssl-users" <[hidden email]>
>
> Hi Ken
>
> I am almost struck in registering the built dll to windows 7 32 bit machine.
>  
> Can you provide me the details on which all openssl1.1.1b output lib files
> and output dll files that needs to be linked to any application while
> building in visual studio??


With mingw, I specify this to the linker

c:/program files/openssl/lib/mingw/libcrypto-1_1.a

In Visual Studio,

Linker - Input - Additional Dependencies: libcrypto32mdd.lib
Linker - General - Additional Library Directory: c:\program files\openssl\lib\vc

However, it sounded like you were linking correctly, but Windows could
not find the dll at runtime.  That points to a PATH issue.

>
> Or any steps needs to be added while building openssl1.1.1b,I am following
> the steps below
> Windows 32-bit
>    1. perl Configure VC-WIN32
>    2. nmake
>    3. nmake test
>    4. nmake install

I don't build myself.  I use Shining Light:

http://slproweb.com/products/Win32OpenSSL.html