Some warnings are out of the user's control, such as the RCC QT bug, or the GNU windres bug, or our informational warning about auto-disabling of options when -Db_bitcode is enabled. Such warnings should not be fatal when --fatal-meson-warnings is passed because there's no action that the user can take to fix it. The only purpose it serves is to prevent people who use those features from using --fatal-meson-warnings.pull/7414/head
parent
99e96133c8
commit
40319c9634
5 changed files with 7 additions and 7 deletions
Loading…
Reference in new issue