8 messages in com.mysql.lists.plusplusRe: linking mysql++ 2.3.2| From | Sent On | Attachments |
|---|---|---|
| Joe Hudson | 30 Nov 2007 16:25 | |
| Warren Young | 30 Nov 2007 22:16 | |
| Joe Hudson | 01 Dec 2007 07:47 | |
| Warren Young | 03 Dec 2007 05:52 | |
| Joe Hudson | 04 Dec 2007 04:49 | |
| Warren Young | 04 Dec 2007 06:38 | |
| Joe Hudson | 07 Dec 2007 09:51 | |
| Warren Young | 07 Dec 2007 14:38 |
| Subject: | Re: linking mysql++ 2.3.2 |
|---|---|
| From: | Warren Young (mysq...@etr-usa.com) |
| Date: | 11/30/2007 10:16:05 PM |
| List: | com.mysql.lists.plusplus |
Joe Hudson wrote:
/usr/local/include/mysql++/common.h:157: error: 'MYSQL_FIELD' does not name a type
I don't see how you can get this error without an earlier one complaining that one of the MySQL C API headers couldn't be found. Regardless, it probably means the directory containing those files isn't in your #include path. How you set that up in Eclipse is something you'll have to figure out; I've only used Eclipse briefly, and it was for PIC microcontrollers, not very high on the list of popular deployment platforms for MySQL++.
(I'm using multiple threads and don't want to define a seperate SSQLS for each thread or put a lock on the .table(str) method between each insert., if that makes any sense..)
Um, no, can't say it does make sense. SSQLS::table() returns a reference to const char*, and the only reason it isn't char* const instead is because you might want to change the table name _once_ if the SSQLS has a different name than the table it belongs to. If you do need that change, it can happen while only a single thread is running, so there's no chance for a race condition.
Unless, I suppose, you're doing something weird like reusing one SSQLS for multiple tables just because they share the same structure. That's just lazy. One table per SSQLS, one SSQLS per table.
/usr/bin/ld: Undefined symbols: Wdbaccesstypes::equity_row::names
You've defined MYSQLPP_SSQLS_NO_STATICS globally instead of defining it for all modules but one. That leaves two statics undefined per SSQLS.
Unfortunately, the complete consequences of this macro were only documented here on the mailing list until recently. It's documented in what will be the v3 user manual (section 5.5, ATM) if you want to check out the svn version and build it....