> From: vin
> To: openssl-users@openssl.org
> Date: 05/10/2019 12:44 AM
> Subject: Re: Issue in linking Openssl1.1.1b to application
> Sent by: "openssl-users"
>
> Hi Ken
>
> I am almost struck in registering the built dll to windows 7 32 bit
machine.
>
&
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 b
> From: vin
> To: openssl-users@openssl.org
> Date: 05/09/2019 01:24 PM
> Subject: Re: Issue in linking Openssl1.1.1b to application
> Sent by: "openssl-users"
>
> Hi Ken
>
> Thanks for the reply.If I am not wrong ,You are asking me to set the path
of
>
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 l
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 fol
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
