Boost.Build v2: Native/non-native wchar_t in msvc toolset

Hi All! I remember that in the first Boost.Build there was an option which allowed to choose whether native wchar_t should be used or typedef-ed to "unsigned short". In v2 the behavior seems to be hardcoded as "always native wchar_t". Is it possible to bring this feature back? -- Alexei Alexandrov

Alexei Alexandrov wrote:
Hi All!
I remember that in the first Boost.Build there was an option which allowed to choose whether native wchar_t should be used or typedef-ed to "unsigned short". In v2 the behavior seems to be hardcoded as "always native wchar_t".
I suppose you are talking about Microsoft compiler? If so, I believe you can get "non-native wchar_t" by passing appropriate compiler flag, either using the <cxxflags> feature or when configuring a toolset. Implementing a generic "feature" to control this does not seem reasonable, given that it's limited to a single compiler. - Volodya
participants (2)
-
Alexei Alexandrov
-
Vladimir Prus