From: Russell Hind (rh_gmane_at_[hidden])
Date: 2004-10-19 09:28:24
> This effectively means that serializing a class defined in one DLL
> from another DLL will not work properly. I've made some changes to
> boost::serialization that allow DLL builds and allow using the library
> modules/DLLs (even when they are explicitly loaded/unloaded multiple
> times), but these changes have not yet made it into CVS.
Is this the same issue? I don't really want to use serialization as
shared library, or access it from shared libraries, I only want to use
it as a lib, but we also use boost thread which, on win32, currently
forces us to build and link everything as dlls so our single exe becomes
a single exe but with a multitude of boost dlls shipped with it
(filesystem, thread) etc.
So that is why I need serialization as a dll because auto-link decides
to use the dll.
Currently, I'm foce-linking to the static lib
(libboost-serialization-bcb-mt-d_1_31.lib) and the stuff is working but
I'd rather auto-link just picked up which dll to use as the rest of
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk