3 ms·

I've noticed a similar problem with C/C++ projects that use -werror. It effectively puts an upper bound on the compiler version used to compile the library when

I've noticed a similar problem with C/C++ projects that use -werror. It effectively puts an upper bound on the compiler version used to compile the library when new warnings are added since the last time the library was updated.

cozzyd 5y ago
Yes it is generally a bad idea to use -Werror in a release build. Fortunately this is easy to fix unlike the library version capping conflict.
Too 5y ago
In Cmake mark third party libraries as SYSTEM. I think this translates to -isystem instead of -i and should not generate warnings.