10 messages in com.mysql.lists.plusplusRe: MySQL++ can be frustrating
FromSent OnAttachments
Jim Langston30 Jun 2006 10:30 
Carlos Flores30 Jun 2006 13:01 
Jim Langston30 Jun 2006 17:09 
Bill K30 Jun 2006 17:37 
Jim Langston30 Jun 2006 22:34 
Carlos Flores04 Jul 2006 07:42 
Warren Young05 Jul 2006 07:34 
Jim Langston06 Jul 2006 02:07 
Robin Stevens06 Jul 2006 10:19 
Warren Young07 Jul 2006 12:52 
Subject:Re: MySQL++ can be frustrating
From:Bill K (rep@billism.com)
Date:06/30/2006 05:37:08 PM
List:com.mysql.lists.plusplus

Hello Jim,

If you mix up the builds (release ad debug) with the wrong LIBs/DLLs, you will get crashing problems as you described.

You need to link the release build to the release LIBs and the debug build to the debug LIBs.

ie: debug build: mysqlppd.lib (Located wherever you put it.) will call mysqlppd.dll (Located wherever you put it.)

release build: mysqlpp.lib (Located wherever you put it.) will call mysqlpp.dll (Located wherever you put it.)

Make sure the paths to the DLL files are in your Windows environmental variable "PATH" or follow rules for side-by-side.

Also, there are 2 MySQL LIBs: libmysql.lib (Normally located in this dir: C:\Program Files\MySQL\MySQL Server 5.0\lib\opt) libmysql.lib (Normally located in this dir: C:\Program Files\MySQL\MySQL Server 5.0\lib\debug)

Jim Langston wrote:

On 6/30/06, Carlos Flores <caf@gmail.com> wrote:

Jim Langston wrote:

I compile the examples and after recompiling the libraries and redirecting where the .lib files are, I get it to work.

So then I am working on my own program, bring in an example and it's crashing on query.storein(res);

I copy the debug libraries from both mysql++ and mysql into the source file, same thing. copy the release files, it just crashes differently.

This is highly frustrating. If the libraries work for some source they would work for the EXACT same source in another directory.

What compiler did you used? which runtime are you using? maybe is a memory issue, it happened to me twice, conflict between msvcrt.dll (used by mingw), msvcrt71 and msvcrt80.dll (last used by VC++ 2003 and 2005 repectively), my VC build enviroment was messed up because i installed msvc 2003 toolkit and VC Express 2005 and changed some linker options so everybody linked against the wrong library.

I'm using Microst Visual C++ .net 2003

Here's the thing that's frustrating me. When I first installed MySQL I was getting this type of error and had to recompile the libraries, and then they worked fine.

I'm copying the .libs and .dlls directly into the program directory in fact to make sure it's using the right directories, still with this problem.

I think I'm going to have to search my hard drive for all instances of libmysql.lib libmysql.dll mysqlpp.lib mysqlpp.dll

and see if I have any that are different.

That is all the libs and dlls I should be concerned with, right?