Hey! The thing is, that the stdcxx reall should behave as if it was part of the compiler, since it's integrated into my wgcc program, so nobody should have to do anything special to use it (no need to define or include anything, it just replaces the MS libc++) The thing is, that i allready got really far with a little patching ;o) the only thing is, that date_time wouldn't build, because of some weird errors in lexical_cast.hpp where some operators are not found. This has to do with not useing /Zc:wchar_t. I don't understand why this breaks compilation, but i didn't want to compile stdcxx with Zc:wchar_t. Since we have an automated build system it would be a great deal of work to change the wchar_t behaviour in all builds. But at the moment i disabled stdcxx, because it didn't work out that good, so we're now waiting for things to get better ;o) Cheers, Markus -----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Jeff Garland Sent: Sunday, September 24, 2006 4:09 PM To: boost@lists.boost.org Subject: Re: [boost] Windows and apache stdcxx John Maddock wrote:

Boris Gubenko wrote:

...

Jeff Garland wrote:

...

As I understand it, Apache stdcxx is derived from the Rogue Wave standard library. This library was used by the Solaris and perhaps some other compiler vendors. HP is one those vendors: HP-UX, Tru64 and VMS all use RW library.

Right, the RW lib should be reasonably well supported by Boost.Config "as is", I think the issue was how to build with the Apache lib when it's *not* the one that comes with your compiler, which I suspect is a bit trickier.

Agree, and I'm sure it's also evolving....so shouldn't we have a new config setup for it that starts from current RW config? Of course to get this right we really need someone to setup at least one test machine... Jeff _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost