List:General Discussion« Previous MessageNext Message »
From:Lars Nilsson Date:June 19 2012 2:24pm
Subject:Re: Unresolved symbols with mysqlclient in DEBUG mode using VC++ 2010 Express
View as plain text  
On Tue, Jun 19, 2012 at 2:48 AM, Miguel Cardenas <renito73@stripped> wrote:
> Hello friends
> 1>mysqlclient.lib(dbug.obj) : error LNK2019: unresolved external
> symbol __CrtSetReportFile referenced in function _DbugExit
> 1>mysqlclient.lib(my_init.obj) : error LNK2001: unresolved external
> symbol __CrtSetReportFile
> 1>mysqlclient.lib(dbug.obj) : error LNK2019: unresolved external
> symbol __CrtSetReportMode referenced in function _DbugExit
> 1>mysqlclient.lib(my_init.obj) : error LNK2001: unresolved external
> symbol __CrtSetReportMode
> 1>mysqlclient.lib(my_init.obj) : error LNK2019: unresolved external
> symbol __CrtDumpMemoryLeaks referenced in function _my_end
> 1>mysqlclient.lib(my_init.obj) : error LNK2019: unresolved external
> symbol __CrtCheckMemory referenced in function _my_end
>
> Do I have to include an aditional library so the symbols are resolved
> correctly? The release mode works perfect and the application runs
> fine in that way only...

The missing functions should be provided by the Visual Studio debug
runtime library. Are all source files in your own code compiled and
program linked with one, and only one, of the flags /MDd (dynamic
linking) or /MTd (static linking)?

Lars Nilsson
Thread
Unresolved symbols with mysqlclient in DEBUG mode using VC++ 2010 ExpressMiguel Cardenas19 Jun
  • Re: Unresolved symbols with mysqlclient in DEBUG mode using VC++ 2010 ExpressLars Nilsson19 Jun
    • Re: Unresolved symbols with mysqlclient in DEBUG mode using VC++ 2010 ExpressMiguel Cardenas19 Jun
      • Re: Unresolved symbols with mysqlclient in DEBUG mode using VC++ 2010 ExpressLars Nilsson19 Jun
RE: Unresolved symbols with mysqlclient in DEBUG mode using VC++2010 ExpressMartin Gainty19 Jun
  • Re: Unresolved symbols with mysqlclient in DEBUG mode using VC++ 2010 ExpressLars Nilsson19 Jun