If you place the curl executable (curl.exe) in a directory that's on your path, you can use curl from a command prompt or batch script without specifying a full path in front of it. You can tell what directories are on your path by bringing up a command prompt (Start Menu -> Programs -> Command Prompt) and typing "PATH". (Actually this really isn't any different than Unix...)

The OpenSSL dlls (libeay32.dll and libssl32.dll) need to be in a directory that's on the path that curl.exe looks at when you run it (assuming you got the curl-ssl package). But if you don't need those dlls for anything else on your machine, it probably makes the most sense to just put the dlls in the SAME directory as curl.exe.

One note on these dlls: libssl32.dll has also been named ssleay32.dll in the past. curl.exe (as compiled by Joern and available at curl.haxx.se) will be looking for that dll named libssl32.dll, however if you manage to compiled curl.exe yourself, you may find that it's looking for that same dll named as ssleay32.dll (that's what I found anyways when compiling with VC6).

--Kevin

>>> Daniel Stenberg <daniel_at_haxx.se> 1/08/01 6:48 PM >>>
The 'nossl' zip file contains only an executable and text files. You may put
the executable file whereever you please. The curl-ssl package differs only
very slightly, and that is the depedence on the OpenSSL dlls. You get the
dlls elsewhere and install them in a suitable place. (The openssl dlls are
usually found from the curl download page as well.)

I'd need more help from windows users to be more specific.
Received on 2001-01-09