C->C++ ported app - unresolved externals
-
I'm porting an old app that was created in VC6 in C-code to VS2005 C++ code. This is an api app that hits a shared lib for interaction with the main app. As soon as I change from C to C++ and build, I have unresolved externals... change back and it builds fine... I've added the project dirs (include and lib), maybe missed something else?? Any ideas? This seems to apply to functions from the shared lib, as well as other c-coded functions in the solution: gen_geo.obj : error LNK2019: unresolved external symbol _rabs referenced in function _make_bbox Thanks
-
I'm porting an old app that was created in VC6 in C-code to VS2005 C++ code. This is an api app that hits a shared lib for interaction with the main app. As soon as I change from C to C++ and build, I have unresolved externals... change back and it builds fine... I've added the project dirs (include and lib), maybe missed something else?? Any ideas? This seems to apply to functions from the shared lib, as well as other c-coded functions in the solution: gen_geo.obj : error LNK2019: unresolved external symbol _rabs referenced in function _make_bbox Thanks
-
Sometimes just stating a problem helps you fix it... A good ole' extern "C" {} around the api #includes did the trick Thanks for allowing me to waste your time :)
:-D A stated problem with a good solution is never a waste of our time, in my opinion. If they have not already, then one of the guys who likes compiling solution faqs will include this. Good work!
INTP "Program testing can be used to show the presence of bugs, but never to show their absence."Edsger Dijkstra