-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
static_wstring
should be conditionally enabled
#51
Labels
Bug
Something isn't working
Comments
Reasonable, I'll take care of this soon |
Please note this was probably because of the standalone library. We would need two paths here. |
@alandefreitas I'm not sure if it's worth trying to replicate |
Probably not. Whatever is easier in standalone. We can have a separate path for boost. |
sdkrystian
added a commit
to sdkrystian/static_string
that referenced
this issue
Oct 24, 2023
sdkrystian
added a commit
to sdkrystian/static_string
that referenced
this issue
Oct 24, 2023
sdkrystian
added a commit
to sdkrystian/static_string
that referenced
this issue
Oct 24, 2023
sdkrystian
added a commit
that referenced
this issue
Oct 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
static_wstring
fails to compile on platforms that don't have libc supportfor wide-character strings. I got it to work by defining a no-op
std::swprintf(...)
, but obviously that isn't really a solution.However, boost::config has feature detection macros for this:
BOOST_NO_CWCHAR
and
BOOST_NO_SWPRINTF
. So ideally,static_wstring
should be conditionallyenabled based on those.
The text was updated successfully, but these errors were encountered: