G
Guest
I'm converting a project from vs2003 to vs2005. The project links against a
thirdparty library (pvrtc.lib, the PowerVR tc compression library), which
apparently was built with some older version of the MS C++ compiler. It is a
static library that has embedded libc.lib dependencies. In my project I want
to link against the MT DLL library (msvcrt), and so in my vs2003 version of
the project I simply specify /NODEFAULTLIB:libc.lib, and things link fine.
When I converted to vs2005, the project file (vcproj file) seems ok, and the
project settings are the same, NODEFAULTLIB:libc.lib is still specified and I
can verify that I am still linking against msvcrt(d).lib, and yet I keep
getting unresolved references to __iob from some of the object files embedded
in the pvrtc.lib library.
I'm completely at a loss here, as __iob is defined in msvcrt(d).lib. So
something is going wrong.
Any ideas? Thanks in advance,
-Eric Twietmeyer
thirdparty library (pvrtc.lib, the PowerVR tc compression library), which
apparently was built with some older version of the MS C++ compiler. It is a
static library that has embedded libc.lib dependencies. In my project I want
to link against the MT DLL library (msvcrt), and so in my vs2003 version of
the project I simply specify /NODEFAULTLIB:libc.lib, and things link fine.
When I converted to vs2005, the project file (vcproj file) seems ok, and the
project settings are the same, NODEFAULTLIB:libc.lib is still specified and I
can verify that I am still linking against msvcrt(d).lib, and yet I keep
getting unresolved references to __iob from some of the object files embedded
in the pvrtc.lib library.
I'm completely at a loss here, as __iob is defined in msvcrt(d).lib. So
something is going wrong.
Any ideas? Thanks in advance,
-Eric Twietmeyer