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
/Werror type commands are a GCC/Clang thing and don't work in Visual Studio. I got around this error by going into my Visual Studio solution and opening up the project properties for the tmxparser project. Under Configuration Properties go to C/C++ and and then Command Line. I removed the /Werror commands from there and those errors were fixed. You could also find where these commands are being set in one of the CMakeLists.txt files and remove them there.
I got a related issue on GCC 12.2.1. It looks like the build arguments should perhaps be removed nowadays.
[1/24] Building CXX object CMakeFiles/tmxparser.dir/src/TmxEllipse.cpp.o
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=strict-prototypes’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=old-style-definition’ is not valid for C++
cc1plus: warning: ‘-Werror=’ argument ‘-Werror=missing-prototypes’ is not valid for C++
Activity
Pingimingi22 commentedon Oct 19, 2021
/Werror type commands are a GCC/Clang thing and don't work in Visual Studio. I got around this error by going into my Visual Studio solution and opening up the project properties for the tmxparser project. Under Configuration Properties go to C/C++ and and then Command Line. I removed the /Werror commands from there and those errors were fixed. You could also find where these commands are being set in one of the CMakeLists.txt files and remove them there.
AzP commentedon Mar 1, 2023
I got a related issue on GCC 12.2.1. It looks like the build arguments should perhaps be removed nowadays.
vanluom123 commentedon May 9, 2023
@AzP I removed flags and it worked fine on CMake to build the library. Thanks!
AzP commentedon May 9, 2023
@vanluom123, I'm happy I could help!
It seems the PR is still not approved though. If the fix isn't in, the bug still exist in the repository, so the bug should be kept open.
vanluom123 commentedon May 10, 2023
Okay, @AzP. I will reopen this issue. It will be closed when PR is merged