Linker errors in VC++ project / unresolved reference to StandardC++ classes???

[aberazioon]

Hi,

I cannot get through with some sort of errors in console project.

Here is an console output:
http://cacheserver.duu.pl/logs/log01.html

Here is an console output (verbose):
http://cacheserver.duu.pl/logs/log02.html


Project had been automatically converted by VC2005 probably from VC6.0.


Project uses some external libraries which seem to cause unresolved
external errors that I can't figure out - symbols refer to some Standard
C++?..

Could someone be so kind and take a look into that? I just quit myself
few hours ago. My clue could be, 3-rd party libraries (those gx*.lib)
used by my project compiled probably against VC6.0 stdc++.

I supposed it's a problem similar to described here (courtesy of google...):
http://www.differentpla.net/content/2006/09/unresolved-external-symbol-std-string-base-xran
however this tip relates to VC2003 and unfortunately doesn't work -
reordering lib dir order in VC options. Some other web links googled out
by me also raise this problem but none gives clear solution but
something like "i got changed this and that and worked for me" with
answer "gosh, for me not...".

Essentially it seems to be __thiscall / __stdcall mismatch. __thiscall
flavor is included in my gx*.lib libraries, while __stdcall flavour is
bound to VC2005.

Soooo... Is VC2005 installation self-consistent when facing backward
compatibility issue like above or should I get older toolset or PSDK, or
what? Of course, getting another gx*.lib compiled against VC2005 is
impossible.

Thanx for any replies
mk

 

[red floyd]

[mostly redacted]

Essentially it seems to be __thiscall / __stdcall mismatch. __thiscall
flavor is included in my gx*.lib libraries, while __stdcall flavour is
bound to VC2005.

Soooo... Is VC2005 installation self-consistent when facing backward
compatibility issue like above or should I get older toolset or PSDK, or
what? Of course, getting another gx*.lib compiled against VC2005 is
impossible.

Well, you *might* try posting in a group where this is on topic, such as
one with Visual Studio, Microsoft, or Visual C++ in its name.

None of your question is addressed by ISO/IEC 14882:2003.