cURL / Mailing Lists / curl-library / Single Mail


Re: Are libcurldll.a and libssh2dll.a meant to be named as such?

From: K. Frank <>
Date: Sun, 18 Aug 2013 12:10:51 -0400

Hi GŁnter!

Thanks for the additional background information.

Also, thanks very much for your libcurl builds!

K. Frank

On Sun, Aug 18, 2013 at 11:45 AM, Guenter <> wrote:
> Hi,
> On 17.08.2013 05:17, K. Frank wrote:
>> I like your reasoning. I don't really know the history and reasoning
>> behind
>> the typical mingw library naming system, and hadn't realized that it
>> limits
>> one's flexibility in choosing which libraries to link statically vs.
>> dynamically.
> this is no typical mingw naming system but the general behaviour of
> windows-targeted configure builds.
>> ...
>> Also, do I surmise correctly that the naming convention for libcurl
>> differs
>> from that of, say, libcrypto because libcrypto is a separate project that
>> you just use, and you don't elect to force your preferred naming
>> convention
>> on them?
> exactly; libcurl and libssh2 are under my control - OpenSSL is not. Beside
> that the naming for libcurl existed already long before I took over
> maintaining the static MinGW makefiles; I just kept it this way, and I
> adopted it to libssh2 ...
> ...
> GŁn.

List admin:
Received on 2013-08-18