Hi,
I'm porting a native app that requires wchar support and STL to Android.
I'm using Dmitry Moskalchuk's (crystax) work for wchar implementations,
and now I'm contemplating on whether to use STLport or libstdc++.
In my particular case, I need -fshort-wchar, which further complicates
matters.
1) STLport comes with a README notice stating it's beta quality
and in particular, it claims exceptions are not supported.
Anyone knows what's up with that?
For the record, stlport/stl/config/_android.h does NOT define
_STLP_NO_EXCEPTIONS.
2) Any reason wstring wouldn't work if I rebuild STLport
with proper, functioning wide string functions?
3) The disadvantage in using libstdc++ is that it has to be built
as part of a toolchain rebuild, which I prefer to avoid (since
I want to enable our devs to use Google-maintained NDKs).
Is there a way to build libstdc++ separate from the toolchain?
The reason for rebuilding is widechar support.
P.S.
What's with STLport's <stdexcept> only including *forward
declarations* of std::string? I understand the desire to speed up
builds, but this is silly. Doing 'throw runtime_exception("something
broke") and the ensuing 'cannot cast const char* to std::string'
is way confusing, and including <string> to solve this
is counter-intuitive.
(If I end up using STLport, I'll probably have an 'stdexcept' of my own
#include_next'ing theirs and then including <string>.)