Re: Singleton MFC Extension DLL
That works for me too Dave, although, most of the time I put it in the Input
line under Linker properties. I know you can also link in libraries using a
pragma as well. Like all this other stuff, there are too many ways to do
the same thing ...
Tom
"David Ching" <dc@remove-this.dcsoft.com> wrote in message
news:#zcvpF$jKHA.1824@TK2MSFTNGP04.phx.gbl...
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:alqck591gias2lej7b560um35fus8qfq0i@4ax.com...
Joe and the others are incorrect. Using Project Dependencies *does* in
fact
cause a link of the associated .lib file. You _do not_ have to add the
.lib
manually to the linker input.
I never had that happen. I always had to manually add it or I would get
undefined symbol
errors.
joe
I don't know what to say. I've been doing it this way for years. I just
verified my .exe has Project Dependencies checkmark for a static lib, and
the static lib is not mentioned in the .exe's Project Properties | Linker
| Input | Additional Dependencies.
-- David