List:General Discussion« Previous MessageNext Message »
From:Miguel Cardenas Date:June 19 2012 3:56pm
Subject:Re: Unresolved symbols with mysqlclient in DEBUG mode using VC++ 2010 Express
View as plain text  
Hello Lars

After hours of testing different project configurations, finally I was
able to compile with debug mode... still pending the test of
debugging, but just created the DLL (it was a library that I'm
developing) without errors...

The configurations I used (VC++ 2010 Express) were:

RELEASE:
- Runtime: /MT (static threaded)
- Library: mysqlclient.lib (...\mysql\lib)
- Ignore library: LIBCMTD.lib (without this does not link the release)
- Debug: NO

RELEASE:
- Runtime: /MTd (static threaded debug)
- Library: mysqlclient.lib (...\mysql\lib\debug)
- Ignore library: <empty> (now allowed LIBCMTD.lib or does not link the debug)
- Debug: YES

If I try to use /MD or /MDd does not compile, if it works with /MT(d)
will leave it that way XD

I'm going to test the debug version (one thing is that compiled and
another one that works =) and if get stuck again will post it...

Thanks for your response

P.D. One last question, is it right to use "...\mysql\lib\debug"
directory for debug version? or it should be set to ""...\mysql\lib"
in both cases and the linker chooses the right one? If compiling in
debug mode it works with both "...\mysql\lib" and
"...\mysql\lib\debug" in DEBUG mode... maybe running the debugger will
not work with the lib, still have to test, but at least it compiles
with no errors... can you comment something about this?

On Tue, Jun 19, 2012 at 2:24 PM, Lars Nilsson <chamaeleon@stripped> wrote:
> 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