LNK 2019 with std::basic_ostream since switch form 2002 to 2003

P

Peter Meier

Hello,

linking external libraries, which linked perfectly under
net 2002 bring up lots of unresolved external symbols for
standard iostream calls: any idea what could cause that or
how to fix that problem?


Greeting Peter


error LNK2019: unresolved external symbol "__declspec
(dllimport) class std::basic_ostream<char,struct
std::char_traits<char> > & __cdecl std::blush:perator<<(class
std::basic_ostream<char,struct std::char_traits<char> >
&,char const *)" (__imp_??6std@@YAAAV?$basic_ostream@DU?
$char_traits@D@std@@@0@AAV10@PBD@Z) referenced in ...

error LNK2001: unresolved external symbol "class
std::basic_ostream<char,struct std::char_traits<char> > &
__cdecl std::blush:perator<<(class
std::basic_ostream<char,struct std::char_traits<char> >
&,class std::basic_string<char,struct
std::char_traits<char>,class std::allocator<char> > const
&)" (??6std@@YAAAV?$basic_ostream@DU?
$char_traits@D@std@@@0@AAV10@ABV?$basic_string@DU?
$char_traits@D@std@@V?$allocator@D@2@@0@@Z...
 
P

Peter Meier

Dynamically linking to mfc solved the problem, although it
does not seem to be the cleanest solution to me.
Any background informations would be nice.

Greetings, Peter
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top