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.
Hi! Sorry to disappoint -- the codebase hasn't been tested against / adapted to VS 2019 yet and all the errors you're seeing are because of that. There is a slight chance things could start to work when you set MSVC2017_COMPATIBILITY to ON (it's a CMake option in Corrade), but I am not 100% betting on that -- so far, with every release of VS there were always new and exciting bugs to work around, so just applying the MSVC2017 workarounds to 2019 might not be enough.
I'll be definitely looking into this and ensuring things work correctly with VS 2019 but right now other things have a priority. Is there a chance you could run on VS 2017 in the meantime?
The MSVC2017_COMPATIBILITY flag apparently works! (at least on this bootstrap/example program) It compiles now but for MSVC compiler only. I've noticed that similar but different error pops up when using llvm tool chain on both 2017 and 2019.
Is clang supported on windows? or am I supposed to use it through mingw?
if not then I'm going to close this ticket now.
Someone tried Clang support some time ago (see mosra/magnum#227 and mosra/corrade#40), but nothing was done since so I guess you'll run into problems there too. MinGW + GCC is known to be working, Clang on other platforms (Linux, macOS, iOS, Android...) is working as well, but frankly I have no idea how it behaves on Windows.
Leave the ticket open as a reminder for me to fix the VS2019 support ;)