Re: Static link problems using VS2005

From:

"David Ching" <dc@remove-this.dcsoft.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Tue, 29 Aug 2006 00:55:24 GMT

Message-ID:

<0gMIg.180$6R7.68@newssvr24.news.prodigy.com>

"Ajay Kalra" <ajaykalra@yahoo.com> wrote in message
news:1156809727.146172.94290@75g2000cwc.googlegroups.com...

"Norbert Unterberg" <nunterberg@newsgroups.nospam> wrote in message
news:OB12F%23eyGHA.3568@TK2MSFTNGP03.phx.gbl...

This sentence is your problem. Static libraries are not linked. When A
is
a static library, it is definately *not* linked against B, C, or D.
Creating a static library is nothing more than droppping all of your
project's OBJ files into one big LIB file. Linking only takes place
when
you create an application or a DLL.

Great observation! We all should have seen it from the beginning.

Thats not true. I dont do it this way for static library. I link
against the .lib file and have not .obj files. It links fine.

That's not what Norbert's saying. He's saying that if lib A depends on lib
B, A doesn't have B's code in it, therefore, any module (.exe or .dll) that
links with A also needs to explictly link with B.

The OP was only linking with A and was wondering why he was getting
unresolved externals for functions in B. This fully explains why.

-- David