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 have had errors with vcpkg libraries where I have forgot to specify an exception handling flag with xmake too. I think this is would be a sensible default flag to add.
/permissive-
I personally think that /permissive- would be a good default too since writing non-conformant code is not the usual use case and not having this causes errors with conforming code, eg with if (x == 1 and b == 2), the C++ and keyword is not permitted.
The text was updated successfully, but these errors were encountered:
Usually xmake will add as few default flags as possible to ensure that users are flexible enough to configure. However, in the new version, users have been able to override the default flags (#978), so adding /EHsc as the default flags is also acceptable.
I have added it in the dev branch, you can update to dev and try it.
However, I still won't add too many default flags. Therefore, I will not add /permissive- yet unless it is really necessary.
/EHsc
/EHsc
is added as a default flag in CMake-produced ninja and msbuild files :from Ninja output
from msbuild output
I have had errors with vcpkg libraries where I have forgot to specify an exception handling flag with xmake too. I think this is would be a sensible default flag to add.
/permissive-
I personally think that
/permissive-
would be a good default too since writing non-conformant code is not the usual use case and not having this causes errors with conforming code, eg withif (x == 1 and b == 2)
, the C++and
keyword is not permitted.The text was updated successfully, but these errors were encountered: