Adds cmake option ENABLE_COMPILER_WARNINGS and fixes compiler warnings#2035
Adds cmake option ENABLE_COMPILER_WARNINGS and fixes compiler warnings#2035purew merged 2 commits intovalhalla:masterfrom
Conversation
ef6d731 to
f1994bf
Compare
|
Running on MacOS with clang I get a few errors we don't see in gcc. I understand we won't track compiler warnings in CI for Mac so would it make sense to fix these here or in a separate PR? I also get errors from rapidjson, a fix for that is in #1864. |
No strong opinions either way but smaller PRs that can be merged faster is usually nicer. |
There was a problem hiding this comment.
why not default on? this would be a good way to annoy everyone into keeping the output warning free
There was a problem hiding this comment.
We discussed before starting this work that having it default on may be untenable due to the multitudes of platform and toolchains we aim to compile on.
A way out of that is to deem one toolchain the one and require no warnings there while being more lenient elsewhere.
kevinkreiser
left a comment
There was a problem hiding this comment.
other than nitpicks looks ok to me
115f072 to
7e32818
Compare
Enables this option on `build-debug` in CI which is deemed _the one_ build to decide on what constitutes a warning. Fixes valhalla#2027
7e32818 to
1d76bb7
Compare
Enables this option on
build-debugin CI which is deemed the onebuild to decide on what constitutes a warning.
Fixes #2027
Tasklist
Requirements / Relations
Link any requirements here. Other pull requests this PR is based on?