If someone comes up with a way to do it. This has a somewhat tortured history. Implementation of export relies on non portable aspects of C++ compilers. Coupled with dynamic loading of libraries it has been difficult to get this working accross all plaforms and circumstances. It has steadily improved to the current state. It's may not be perfect, but its much better than it used to be and quite servicable. Robert Ramey Kenny Riddile wrote:
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?