This has caused problems in the past. I believe that the code checked into the current HEAD branch of the CVS tree addresses this, but I havn't been able to test it. My intention was the BOOST_CLASS_EXPORT would be included in the *.h file for the class. My recommendation is to make a library which instantiates all your classes's serialize functions with all the archives you're going to use. Then link against this library. Robert Ramey Sohail Somani wrote:
Hi,
Is there any danger in having multiple BOOST_CLASS_EXPORTs within a shared library or executable? I have a template child class that is always serialized by base class pointer and to keep myself sane I figure I can just blindly add BOOST_CLASS_EXPORT(ChildClass<T>); at the end of the .cpp file that uses it.
Thanks,
Sohail