static lib link errors VS2013

What are your project's settings, i.e. what is selected under "Configuration Properties|C/C++|Code Generation" as "Runtime Library" and what is "Configuration Properties|Linker|Command Line"?

Thanks for the Quick response jkr. I've attached a PDF  file with screen captures of the settings you asked for.
LIB-settings.pdf

Ah, you have '/NODEFAULTLIB' set. This makes the linker ignore all default libraries, as the name implies. Remove that by going to "Linker|Input" and set "Ignore Default Libraries" to "No".

Hello jkr, I tried what you suggested and there was no change in the linking errors. they are identical to the original errors. I verified that the change was actually done, and did a rebuild just in case.

a static library is a container of object modules which is equivalent to a folder containing object files. because of that, different compilers may produce different object code which cannot be linked together. for example if the vs2008 code calls a c++ function which is no longer available in vs2013 or has different arguments, the linker would not be able to solve this. worse,  a new compiler even could have changed the c++ name mangling (which puts some decoration around function names such that t

the best way out is to follow the advice HooKooDooKu gave and port the static library to vs2013. that solves the issue if the project builds correctly.

Sara

I ended up scrapping it since time was running out. The 'Best Solution' got me the closest to having it fixed.