At 10:31 AM 11/5/2002 -0500, Oblio writeth:
>Wow, this is great! This will save me a lot of time mucking about with
>trying to get the compiler to run. Quick question, though. The main file,
>openssl.exe, is looking for two files in the path (ssleay32.dll and
>libeay32.dll). What are these, and where do they come from?
These should have been copied to your c:\windows\system32 directory during
the installation process. This is to simplify life so that the DLLs are
available to all applications (and so the end-user doesn't have to copy
them to some location).
Unfortunately, I just realized that there are various forms that the DLLs
have taken. Running openssl.exe on my test machines works fine since I
have all of the various forms of OpenSSL available, but you do not
necessarily have them.
Quick fix: Copy the libssl32.dll file located in the c:\windows\system32
(or c:\winnt\system32) directory. Paste into the same directory. Rename
the new file (usually "Copy of libssl32.dll") to ssleay32.dll. Try running
openssl.exe (you should be at a prompt of sorts). This problem will be
fixed in the next Win32 OpenSSL Installation Project release.
While the above quick fix works, your code should rely on libssl32.dll and
libeay32.dll as that is what is "standard" and the use of ssleay32.dll is
considered to be a legacy name (more or less).
Hope this helps!
Thomas J. Hruska -- [EMAIL PROTECTED]
Shining Light Productions -- "Meeting the needs of fellow programmers"
http://www.shininglightpro.com/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
