aboutsummaryrefslogtreecommitdiff
path: root/share/pixmaps/bitcoin64.png
diff options
context:
space:
mode:
authorCory Fields <cory-nospam-@coryfields.com>2016-03-09 16:45:58 -0500
committerCory Fields <cory-nospam-@coryfields.com>2016-04-27 01:17:14 -0400
commit63b3111f84daa421abc2889a550e86c17bf9609d (patch)
treeb83930ad73ec9e693880a38c4ca3e87ec04d1cf2 /share/pixmaps/bitcoin64.png
parente26b62093ae21e89ed7d36a24a6b863f38ec631d (diff)
build: quiet annoying warnings without adding new ones
Disabling warnings can be tricky, because doing so can cause a different compiler to create new warnings about unsupported disable flags. Also, some warnings don't surface until they're paired with another warning (gcc). For example, adding "-Wno-foo" won't cause any trouble, but if there's a legitimate warning emitted, the "unknown option -Wno-foo" will show up as well. Work around this in 2 ways: 1. When checking to see if -Wno-foo is supported, check for "-Wfoo" instead. 2. Enable -Werror while checking 1. If "-Werror -Wfoo" compiles, "-Wno-foo" is almost guaranteed to be supported. -Werror itself is also checked. If that fails to compile by itself, it likely means that the user added a flag that adds a warning. In that case, -Werror won't be used while checking, and the build may be extra noisy. The user would need to fix the bad input flag. Also, silence 2 more additional warnings that can show up post-c++11.
Diffstat (limited to 'share/pixmaps/bitcoin64.png')
0 files changed, 0 insertions, 0 deletions