On 2/24/2016 2:32 PM, Jeanne Vural wrote:

Can I install multiple curl versions on same server to use for end user ftp and sftp commands?

I have some existing code that uses curl 7.32.0 that I don’t want to risk breaking.

However I need the sftp functionality offered by version 7.41.1.



Please consider using the latest version of curl for security and stability. Like literally every week curl is improved, and then usually every two months there is a new release with those improvements.
https://curl.haxx.se/download.html#Win32

To answer your question, yes you can do that. Since you use Windows the biggest issue to be aware of is DLL dependency conflicts. Unless you have at least one fully static version of curl (ie a version of curl with no dependencies other than Windows) do not attempt to move it into the directory of the existing curl that you want to keep.

If your version of curl is not fully static it will depend on at least libcurl and at most other libraries as well like libssh2. The way curl works is it uses the library libcurl to make the transfers, so if you just copy the newer curl.exe that is not fully static to that existing directory it could use the old libcurl DLL. In other words you end up running curl 7.41.1 but it uses libcurl 7.32 which is not what you want.

The easiest way to see what your version of curl supports and make sure you are using the right libcurl is by running curl -V at the command prompt. You will see something like this: curl 7.47.1-DEV (i386-pc-win32) libcurl/7.47.1-DEV OpenSSL/1.0.2f nghttp2/1.7.1 Protocols: dict file ftp ftps gopher http https imap imaps ldap pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS Debug Largefile NTLM SSL HTTP2

Note that the curl and libcurl version numbers match, 7.47.1-DEV. If it supports sftp it will say that in protocols and there will be a line like libssh2/1.7.0
-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:  https://curl.haxx.se/mail/etiquette.html

Reply via email to