You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm building on a system with -fno-exceptions.
The only way I found to prevent the throw statement from leading to a compiler error is defining RUST_CXX_NO_EXCEPTIONS in the CXXFLAGS env var as it's read by cc.
I don't want to set this as a global define for all builds using the environment variable if possible.
Is this the preferred solution or am I missing something?
If this is currently the preferred way of dealing with this would you be open to exposing this (and maybe exception handling in the crate in general) through a feature flag?
Or would you prefer a more implicit solution like #1174?
The text was updated successfully, but these errors were encountered:
Hi,
I'm building on a system with
-fno-exceptions
.The only way I found to prevent the
throw
statement from leading to a compiler error is definingRUST_CXX_NO_EXCEPTIONS
in theCXXFLAGS
env var as it's read bycc
.I don't want to set this as a global define for all builds using the environment variable if possible.
Is this the preferred solution or am I missing something?
If this is currently the preferred way of dealing with this would you be open to exposing this (and maybe exception handling in the crate in general) through a feature flag?
Or would you prefer a more implicit solution like #1174?
The text was updated successfully, but these errors were encountered: