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
Hm, I don't feel like adding workarounds for broken compilers, sorry 😅
What you could do is to not build Corrade with -std=c++20, it only makes the build slower for no reason. Then it won't / shouldn't include the C++20-specific <numbers> header and thus should circumvent this error.
target_compile_features(${PROJECT_NAME} PUBLIC cxx_std_20)
instead of
SET(CMAKE_CXX_STANDARD 20)
does get past this specific problem.
I'm fine if you want to close this issue.
mosra
changed the title
Windows mingw Corrade/Corrade\Utility\Path.cpp
Building Corrade with -std=c++20 causes errors inside MinGW <numbers> header
Sep 23, 2022
I edited the issue title to make it easier to find when someone else hits the same issue, but I'm going to close it, yes -- this is a STL bug, not something a library should be fixing from outside.
See this workflow run: https://github.com/jonesmz/osp-magnum/runs/8295901356
I don't know why this is happening, but i can confirm that adding
-fext-numeric-literals
to the compiler options does fix it.Perhaps Corrade could add the flag if mingw is detected?
The text was updated successfully, but these errors were encountered: