John Maddock wrote:
It looks to me that there are only a couple of undefined symbols because the serialization autolink code is being enabled by BOOST_HAS_DECL which is now being used to enable "visibility". This is likely even more confused as I believe I've used this or something like it to trick the compiler/linker into suppressing code stripping of code not otherwise explicitly referred to.
GCC's visibility feature is actually very similar to msvc's import/export feature - just a different name. Using it to prevent code being stripped will continue as before for msvc, and probably have no effect (as before) for gcc.
Hmmm - now I'm wondering about code stripping in gcc. Why is this not a problem for this compiler? Does it never strip code? Does it depend on compile time switches that we don't user or ???. To my mind, the problem is that the library depends on behavior outside the scope of the C++ standard so we sort of end up addressing these issues by trial and error. It seems the whole subject of runtime linking is basically undefined.
Cheers, John.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost