Here I have tried to describe, the environment/affecting parameters, in
which I am trying to use CURL. Ofcourse, MFC has nothing to do with what
CURL does, it describes the way my shared library is being built.
Yes, MSVCRT.LIB is thread-safe version of LIBCMT.LIB. Both libraries
have their implementation of some commonly used functions/operators like
DllMain(), new(), delete() and so on. My question is, whether CURL
ALWAYS requires CRT library like LIBCMT.LIB?

-----Original Message-----
From: Daniel Stenberg [mailto:daniel_at_haxx.se]
Sent: Tuesday, April 30, 2002 3:00 AM
To: Mandar Wadekar
Cc: libcurl Mailing list
Subject: Re: CURL compatibility

On Tue, 30 Apr 2002, Mandar Wadekar wrote:

> I am trying to use CURL in a shared library (uses MFC as shared DLL)
which
> links with MSVCRT.LIB. During build there are no linker
errors/warnings.
> But curl_easy_perform() throws exception. It works fine if link with
> LIBCMT.LIB and with NO MFC.

Sorry, this is highly windows-specific stuff and I have no idea what
this
means.

Could it be that MSVCRT.LIB is not the thread-safe version but
LIBCMT.LIB is?
I really don't understand how the MFC stuff has anything to do with what
curl
does...

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth_at_sourceforge.net