Re: Static library(.lib) v/s dynamic library(.dll) size confusion

From:

David Wilkinson <no-reply@effisols.com>

Newsgroups:

microsoft.public.vc.language

Date:

Fri, 13 Nov 2009 07:02:41 -0500

Message-ID:

<u#44wkFZKHA.5620@TK2MSFTNGP06.phx.gbl>

Nathan Mates wrote:

In article <39b33070-4864-4695-a1ff-728f3f767ffb@y28g2000prd.googlegroups.com>,
Nithin <nithin.papdeja@gmail.com> wrote:

My question is even though I have the same number of files in both
cases why is static library(.lib) size so large??I am working in some
embedded project so size is a major constraint

Because when you choose to use the C Runtime (aka CRT) libraries in
a static configuration, then any functions you use from the C Runtime
libs (starting with basics like printf, and going up from there) must
be embedded in your .lib. That's the definition of static
linking. Dynamic linking to the CRT means that those functions from
the CRT are loaded from a shared .dll, so they don't need to be in the
.lib.

OP is talking about a static .lib project versus a dynamic .dll project, not
about static versus dynamic linking of CRT. These, I think, are orthogonal issues.

To the OP: how are you linking to CRT in these projects?

--
David Wilkinson
Visual C++ MVP