On Mon, Dec 8, 2008 at 4:21 PM, Kenny Riddile
Ah, well I finally happened across this link: http://www.boost.org/doc/libs/1_37_0/libs/serialization/doc/special.html#exp...
which contains the blurb:
"Also, when making shared libraries, there is currently a restriction that only one such library can use BOOST_CLASS_EXPORT for any given type. All this will most likely make it inconvenient to include BOOST_CLASS_EXPORT as part of the header of the class to be serialized. So, the best way to use BOOST_CLASS_EXPORT is to include it in the same module which implements the class."
Are there any plans to remove this restriction somehow in the future?
As Robert pointed out, BOOST_CLASS_EXPORT relies on platform-specific hacks to work, but note that you *can* use boost.serialization without BOOST_CLASS_EXPORT. Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode