c++ - VC++ project using unmanaged DLL in a multi-project solution causes linking errors when building -
i have strange problem multi-project solution in vs 2010. had solution single project in c++/clr interfaced third-party unmanaged dll. now, moved project multi-project solution. double-checked include / additional library parts correct (i have problem when set absolute paths include , lib dir) , .lib accompanying third-party dll correctly referenced.
now, when trying build project, bunch of lnk2028, lnk2019, lnk2020 , like.
however, when create single solution project, builds fine.
does vs2010 not support multi-project solutions when 1 project references unmanaged code?
edit: investigated more, here happens:
- opening project in single solution => builds fine.
- adding same project existing solution => linker errors
- adding new project solution single vc++ project => builds fine.
*bangs head on keyboard* solved it! has nothing location of project! noticed solution built correctly when using release configuration, debug causes linker errors. turned out tried link against third-party .lib file release mode in debug mode. changed debug settings use debug-mode lib file in debug mode , builds.
Comments
Post a Comment