15 messages in com.mysql.lists.plusplusRE: MYSQLPP problem in visual studio ...
FromSent OnAttachments
Graham Reitz06 Aug 2007 14:14 
William F. Dowling06 Aug 2007 14:20 
Graham Reitz06 Aug 2007 14:26 
Graham Reitz06 Aug 2007 14:31 
Graham Reitz06 Aug 2007 14:48 
Cedrik Magis07 Aug 2007 01:55 
Michael Nye07 Aug 2007 01:59 
Jim Wallace07 Aug 2007 04:04 
Ian Daysh07 Aug 2007 04:16 
Cedrik Magis07 Aug 2007 04:32 
Jim Wallace07 Aug 2007 06:38 
Ian Daysh07 Aug 2007 10:38 
Graham Reitz07 Aug 2007 20:45 
Warren Young09 Aug 2007 05:01 
Graham Reitz10 Aug 2007 17:42 
Subject:RE: MYSQLPP problem in visual studio : mysqlpp.dll was not found !!!
From:Ian Daysh (I.Da@sstl.co.uk)
Date:08/07/2007 10:38:07 AM
List:com.mysql.lists.plusplus

Sorry Jim, this meant to go to the whole list:-

In the readme.vc file, it does mention about DLL location (see paragraph
starting at line 31 - "Be sure to build both.....")

Granted, Windows is a pain in the arse when it comes to DLL's and all.

-----Original Message----- From: Jim Wallace [mailto:jwal@kaneva.com] Sent: 07 August 2007 14:39 To: plus@lists.mysql.com Subject: RE: MYSQLPP problem in visual studio : mysqlpp.dll was not found !!!

This is nothing specific to MySQL++. It's just how Windows works.

I don't think the MySQL++ doc would be deficient for not telling a developer how
Window finds DLLs.

This is in the documentation, is it not??

Yes, the DLL must be in the folder with your exe, or in one of the folder in the
PATH.

-----Original Message----- From: Michael Nye [mailto:mich@jcu.edu.au] Sent: Tuesday, August 07, 2007 5:00 AM To: plus@lists.mysql.com Subject: Re: MYSQLPP problem in visual studio : mysqlpp.dll was not found !!!

Hi Cedrik,

I too had this problem. I think there is a number of fixes for the problem, but
the simple way I solved it was by including the .dll in the location of the
.exe. In VS2005 this means that in the debug/release folders within your
program, and possibly in the main project folder too. I'm pretty sure you can
setup the compile so it references to the .dll location (or you might have to
play with Windows not the compile to do this) but couldn't be bothered exploring
further after I found this simple way out.

Cedrik Magis wrote:

Hello,

We've got a problem in the use of the mysqlpp library, when using it in our
program and even with the example project mfc in visual studio (2005
professional edition). There is no problem in compiling, only when launching the
.exe. We've got an error message : "This application has failed to start because mysqlpp.dll was not found.
Re-installing the application may fix the problem."

In our compiling options, the address of the mysqlpp.dll is correct (and, even
it's obvious, myslpp.dll is present), if some has encountered the same problem
or can help us to understand this, we will be grateful.

Thanks,

Cedrik and François

-----Original Message----- From: Graham Reitz [mailto:grah@mac.com] Sent: Monday, August 06, 2007 11:49 PM To: will@thomson.com Cc: plus@lists.mysql.com Subject: Re: multiple definitions of symbol linker error using sql_create_#

Ok I see what is going on now.

From another post:

To fix this, I would put the sql_create_* macro in a separate .h

file, > and #define MYSQLPP_SSQLS_NO_STATICS above all #includes for that file > except for one. This ensures that the static members are assigned to > only once. You can see this pattern in action in the examples: the > 'stock' SSQLS type is defined in stock.h, and it is included in both > util.cpp and in custom*.cpp

That is an unfortunate thing to have to do, especially if you will be sharing a library with other developers. Now they have to 'remember' to do this. Easy enough to do, but when you get busy it can be easy to forget or overlook.

On Aug 6, 2007, at 4:21 PM, William F. Dowling wrote:

Put something like this in the project .h file (say, projdb.h):

#ifndef PROJ_DB_CPP #define MYSQLPP_SSQLS_NO_STATICS #endif

and something like this in the one corresponding .cpp file

#define PROJ_DB_CPP #include "projdb.h" #undef PROJ_DB_CPP

This caught me up too; search the mail archives for a fuller explanation.

On Mon, 2007-08-06 at 16:14 -0500, Graham Reitz wrote:

I created a header file where I placed all of my sql_create_# macros.

I keep getting multiple definition linker errors.

/usr/bin/ld: multiple definitions of symbol agencies::names (there are more, but similar)

What am I missing?

The code looks as follows:

// start file my_tables.h #include <mysql++.h> #include <custom.h> #include <string>

#ifndef _TABLES_HPP_ #define _TABLES_HPP_

sql_create_3(agencies, 1, 3, unsigned int, agency_id, std::string, agency_name, std::string, agency_contact)

sql_create_3(billing, 1, 3, unsigned int, billing_id, std::string, billing_agency_name, std::string, billing_first_name) #endif // _TABLES_HPP_ // end file my_tables.h

// start file my_db.h #ifndef _MY_DB_H_ #define _MY_DB_H_

#include <string> #include <vector>

#include <boost/noncopyable.hpp> #include "my_tables.h"

class my_db : boost::noncopyable { public: explicit my_db(std::string tcp_ip_address, unsigned int port_number, std::string db_name, std::string db_username, std::string db_password); }; #endif // _MY_DB_H_ // end file my_db.h

// start file my_db.cpp #include <mysql++.h> #include "tac_db.h"

my_db::my_db(std::string tcp_ip_address, unsigned int port_number, std::string db_name, std::string db_username, std::string db_password) { // Connect to the database mysqlpp::Connection connection(db_name.c_str(), tcp_ip_address.c_str(), db_username.c_str(), db_password.c_str(), port_number, false); } // end file my_db.cpp