Re: Singleton MFC Extension DLL
"Ajay Kalra" <ajaykalra@yahoo.com> wrote in message
news:16c3c820-a9c7-49cb-99e6-31724452b1ac@j1g2000vbm.googlegroups.com...
On Jan 7, 4:41 pm, "David Ching" <d...@remove-this.dcsoft.com> wrote:
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.
Well.. Live and learn. I had no idea this even existed. Also, it
doesnt make much sense to me as you shouldnt have one project change
other project. In addition, this has side effect of not working if you
compile/link the project(which depends upon the lib) by itself. This
will work if solution itself is compiled.
It works beautifully in this case. If your .lib changes and you rebuild the
lib project only, the next time you build the .exe which depends on it it
will see the .lib has changed and relink. It's even better. If you change
a .cpp file in the .lib and rebuild the .exe, it will first build the .lib,
then build the .exe. It's all as it should be.
-- David