
Note that there is a distinction between between support for wchar_t and wstreambuf. The former is supported by all archives. The latter is supported only by those archives compiled into the wserialization library. My experience is that gcc and mingw on windows doesn't support wstreambuf and hence doesn't support wstream. Note that in the boost testing matrix, tests with the wide char streams are failing for these compilers. This is the reason. I've managed to get the boost build system to skip the tests on the future for wide char archives. Note that this is not a boost serialization issue but one of wide streams with gcc libraries on windows. Also check out the boost tests -see config - for these compilers. you'll notice that these indicate that wide stream i/o is not supported. If this is an issue for you the best way to address is to find, make, port, or ? a wide char i/o library for gcc and windows - or use a different compiler. Robert Ramey Hin-Tak Leung wrote:
manphiz wrote:
chun ping wang wrote:
is their any ways for fix around this?
using gcc mingw 3.4.5
IIRC, MinGW 3.4.5 doesn't have wchar.h, or wchar_t is not supported, which should be detected by bjam and disable all the wide char version in Boost like boost.wserialization, boost.wregex, etc. <snipped>
Hmm, I don't have native mingw, but I have the mingw cross compiler suite under linux and it has wchar.h, and also wchar_t is referred to inside wchar.h and wctype.h . But, wchar.h and wctype.h should be part of mingw-runtime or w32api (and I have cross-compiled and installed very recent version of both as part of the cross-compile suite) rather than gcc per se.
HTL