Re: problem using static libcurl

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Wed, 1 Aug 2007 11:40:01 -0700

Message-ID:

<eb7jdtG1HHA.5532@TK2MSFTNGP02.phx.gbl>

You are misrepresenting the original reply. We are talking
about all libs statically "linking" against the same CRT flavor.
Since static libs do not link, the EXE gets a single copy of the
common CRT flavor statically linked and Scott's assertion
is wrong. That's what Ben's comment is about. His clarification
concerns the fact that multiple CRT copies would be in use
in the case of DLLs, not static libs.

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

"David Wilkinson" <no-reply@effisols.com> wrote in message
news:uGm%23uZF1HHA.4184@TK2MSFTNGP06.phx.gbl...

David Lowndes wrote:

This sounds like what is typically caused by using static linking to
the C runtime library. If both your server and your lib link
statically to

No.

the runtime lib then you get two copies of the runtime lib, and so two
heaps. The libs don't recognize pointers to each other's heaps.

If both an exe and dll statically link the CRT, you get two heaps. If
the library is statically linked, it *can't* get its own copy of the
CRT.

Err - what are you saying Ben? What Scott wrote made sense to me.

Dave:

What Ben said sounded right to me. If I link libcurl.lib into Ben.exe,
doesn't all the code necessarily use the same heap? If the .lib is
compiled with a different CRT setting from the main project, won't that
generate library conflicts in the linker (possibly resolvable by using
NODEFAULTLIB)?

--
David Wilkinson
Visual C++ MVP