Hartmut Kaiser wrote:
Ok, here is what I got. Everything suddenly starts to work as soon as there is at least one BOOST_CLASS_EXPORT() inside a shared library which is loaded at application startup (not loaded with dlopen()).
LOL - this is the kind of thing that in a million years would not have occurred to me.
But please don't ask me why, it's just good to know. Perhaps we're dealing with some idiosyncrasies of the dlopen() library in combination with gcc symbol visibility rules.
I would guess a more likely (and perhaps fixable) cause. The serialization::singleton guarentees that and instance of an object is initialized before first usage. Perhaps something isn't being used "soon enough" when all exports are in DLLS. It has been found that in gcc compilers, static destructors are not called in reverse order of invokation of static constructors. This is the function is "is_destroyed". My guess is that there is something which should be forced to be initialiezed at application startup. looks like we'll have to wait and see what it is. Robert Ramey
Problem solved, thanks again! Regards Hartmut
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost