On Friday 09 February 2007 11:28, Vladimir Prus wrote:
The link errors we get with msvc 7.1 and stlport are caused by wchar_t mismatch. 7.1 defaults to non-native wchar_t and default stlport build uses that default. Boost.Build explicitly enables wchar_t as native type, so when using non-native-wchar_t-build stlport, we get linker errors.
Solutions are:
1. Disable native wchar_t in Boost.Build for STLPort configurations. 2. Build STLPort with native wchar_t
Do folks with practical experience with msvc 7.1 and stlport have an opinion which one is better?
If (2) is better, is the procedure for buildind stlport with native wchar_t documented anywhere?
I'd say (1) - there are commercial libraries out there that assume (1) is true and that won't like if it isn't. Been caught out by this when trying to migrate some code to msvc 8.0 as that assumes that wchar_t is a built-in type. Regards, Timo