[vtkusers] building vtkMFC as a static library (Visual studio 2008)
Mark Gooding
mark.gooding at gmail.com
Wed Sep 2 04:35:18 EDT 2009
2009/9/1 John Drescher <drescherjm at gmail.com>:
> I would suggest using cmake to generate your project files for visual
> studio for your main application. It is much easier handling all the
> needed dependencies that way and it also adds functionality to the
> project.
> ...
if it makes my life easier I've no real objection to using cmake, but
it would need me to learn that. How steep is the learning curve?
> If you do not want to go this way. Take a look at each unresolved
> external and google a few to determine what library needs to be added.
> This is not as hard as it seems.
Turned out to be project configurations rather than missing libraries.
My MFC project was set to 32bit and vtk was compiled as 64bit. After
fixing that I now get different (and even more exciting?) errors...
all 1724 of them... all LNK2005 errors "blah blah is already defined".
More information about the vtkusers
mailing list