>Exactly! Welcome to the club. A good number of the products one trials or >purchases over the years install their own copy of the OpenSSL DLLs >*somewhere*. Use the Windows Start search function and key in ssleay32.dll >and/or libeay32.dll and see how many hits you get! You could start by >uninstalling or deleting any products you are sure you are not using. (Don't >just delete them all!) Perhaps that will solve the problem.
>Else, you are *probably* going to get the correct DLL if you put it right in >the same folder with your .exe. Copy your DLLs from wherever you built them >to wherever you are building your application. It's a little complicated >with VS because of the multiple folders: project, Debug, and Release -- but >play around and you should be able to get it right. >You are in my experience on the right track using SSLeay_version(). I would >leave it in my code and printf the results on every execution. You never >know when someone is going to install *something* and mess you up. >Good luck! >Charles You're right. There is a lot of Openssl libs into my pc. So, I've looked for the one which was 0.9.8 version. It was in "C:\Windows\System32" and when I was compiling, QT was loading from there. I've copied ssleay32.dll and libeay32.dll to the same directory as my App.exe. Now it's working with the right version. I've prepared the installation package to copy this, too. Now, it's "just" program the myLib. :P Thank you all for helping. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
