Didn't we have a similar problem in 2.2.3, where the MYSQLPP_EXPORT was in
front of classes, like one derived from std::vector< std::string> giving the
same linker error, and it was not necessary to export them to the
mysqlpp.dll?
The fix to this problem was to remove the "MYSQLPP_EXPORT" in front of the
class FieldNames. This was the release after 2.2.3, where this error
occurred.
I did not find anything similar in the 2.3.2 version. But I might not see
it.
So the question is - which version of the library are you using? Please make
sure you have the latest.
If it is the latest, Warren might know which classes/functions were added
with the "MYSQLPP_EXPORT" since the fix for 2.2.3, which might not need to
be exported?
I hope this helps
Nils
-----Original Message-----
From: plusplus-return-7015-nilswoetzel=web.de@stripped
[mailto:plusplus-return-7015-nilswoetzel=web.de@stripped] On Behalf
Of Warren Young
Sent: Monday, September 17, 2007 5:41 PM
To: MySQL++ Mailing List
Subject: Re: vector error ( LNK2005)
Dale Stewart wrote:
> I think that the cause of this error is due to a mismatch in the C
> runtime library
I agree, but also:
> (??0?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@ABV
> 01@@Z) already defined in mysqlpp.lib(mysqlpp.dll) StructTables.obj
...how in the world did a "StructTables.obj" get into mysqlpp.dll? If
you're doing something weird with the library, it's no wonder you're
getting weird errors.
--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsub=1
