[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug-wget] DLL conflict between wget and curl
From: |
Jeremy Nicoll - ml wget users |
Subject: |
[Bug-wget] DLL conflict between wget and curl |
Date: |
Fri, 27 Apr 2012 21:16:09 +0100 |
User-agent: |
Messenger-Pro/2.68.5.3631 (Qt/4.7.3) (Windows-XP) |
Win-32 XP Pro SP3
A few hours ago I downloaded cURL, unpacked its zip, and moved the exe and
necessary DLLs to the folder where I keep CLI programs. That is:
curl.exe 659 KB V7.25.0.0
libcurl.dll 529 KB V7.25.0.0
libeay32.dll 1516 KB no version number
libssl32.dll 345 KB no version number
Then I moved on to do the same for wget. But the dependencies zip comes
with 4 DLLs:
libeay32.dll 1150 KB V0.9.8.8
libiconv2.dll 985 KB V1.12.2872.39125
libintl3.dll 101 KB V0.14.4.1952
libssl32.dll 228 KB V0.9.8.8
Clearly I can't put the libeay32 & libssl32 DLLs supplied with wget into the
same folder as the two that came with curl. And because Windows Explorer
shows no version number info for the ones that came with curl, I don't know
which ones are the more recent versions.
Even if I did know that, I don't know whether it's good practice to keep
each exe with the specific versions of DLLs it was shipped with (though I
suspect that IS the best method) or whether one should just install the most
recent version of each libxxxx.dll and hope.
If the DLLs need kept separately then it follows that neither set should be
in a folder on PATH, and I suppose that neither curl.exe nor wget.exe should
be either. Is the solution to this problem to put each app in its own
folder and alway specify the path to the exe when I want to use it?
--
Jeremy C B Nicoll - my opinions are my own.
- [Bug-wget] DLL conflict between wget and curl,
Jeremy Nicoll - ml wget users <=