Visual Studio's 2005 question

[joshturner1967]

Hello I apologzie if I have this in the wrong group but I tried the
moderated comp lang moderated C group and they suggested I try a
windows group. After further seaching I came across this group and I
know it's not an exact match but I was wondering if you guys could
help me out.


I have several projects written C that interacts with a third party
api. This third
party has a library that compiles and links in VS 2005 lets call it
pnznmapi55.lib. However when I take the same code swap out the
includes
and the libs for an upgraded version of 58 and of course using
pnznmapi58.lib
then it will compile but will not link.

I have my additional link lib directory set to the path of the lib and
I also have the actual lib mentioned in the addtional dependencies.
This is standard for what we did for the old lib and also standard for
what we did for the old lib in Vs 2003 as well. I am confused as to
what the problem might be. The third party is trying to say that it's
because I don't have my environmental variables setup properly for
2005 but if that is the case then why would it work for 55 but not 58
of the lib. The link messages that I am getting is the standard
lnk2001 here is an example


pnznmapi.lib(tdebug.obj) : error LNK2001: unresolved external symbol
_pnz_errfrm_unmark_API

As you can see it all comes back to the pnznmapi.lib which is the lib
I am specifically linking too in my link sentings - I have no control
over _pnz_ type symbols since they are internal third party code.

Anybody have any ideas? I am stumped

Thanks
Josh

 

[PvdG42]

Hello I apologzie if I have this in the wrong group but I tried the
moderated comp lang moderated C group and they suggested I try a
windows group. After further seaching I came across this group and I
know it's not an exact match but I was wondering if you guys could
help me out.


I have several projects written C that interacts with a third party
api. This third
party has a library that compiles and links in VS 2005 lets call it
pnznmapi55.lib. However when I take the same code swap out the
includes
and the libs for an upgraded version of 58 and of course using
pnznmapi58.lib
then it will compile but will not link.

I have my additional link lib directory set to the path of the lib and
I also have the actual lib mentioned in the addtional dependencies.
This is standard for what we did for the old lib and also standard for
what we did for the old lib in Vs 2003 as well. I am confused as to
what the problem might be. The third party is trying to say that it's
because I don't have my environmental variables setup properly for
2005 but if that is the case then why would it work for 55 but not 58
of the lib. The link messages that I am getting is the standard
lnk2001 here is an example


pnznmapi.lib(tdebug.obj) : error LNK2001: unresolved external symbol
_pnz_errfrm_unmark_API

As you can see it all comes back to the pnznmapi.lib which is the lib
I am specifically linking too in my link sentings - I have no control
over _pnz_ type symbols since they are internal third party code.

Anybody have any ideas? I am stumped

Thanks
Josh

Sorry to send you on your way again, but this is a .NET programming group.
Best "Windows" groups for your C question would be:

microsoft.public.vc.language

or other groups in microsoft.public.vc.*