summaryrefslogtreecommitdiff
path: root/mesonbuild/modules/windows.py
diff options
context:
space:
mode:
authorNirbheek Chauhan <nirbheek@centricular.com>2020-07-01 06:52:56 +0530
committerJussi Pakkanen <jpakkane@gmail.com>2020-07-05 16:13:00 +0300
commit40319c963447f7632753e694f606dc6d41a9f168 (patch)
tree9e7a316efc3646df971acaa27b12d7a83e170d65 /mesonbuild/modules/windows.py
parent99e96133c83aa61ab39c3d35c3248ca05fdb7ada (diff)
downloadmeson-40319c963447f7632753e694f606dc6d41a9f168.tar.gz
Don't make unactionable warnings fatal
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.
Diffstat (limited to 'mesonbuild/modules/windows.py')
-rw-r--r--mesonbuild/modules/windows.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/mesonbuild/modules/windows.py b/mesonbuild/modules/windows.py
index b3e498304..605070542 100644
--- a/mesonbuild/modules/windows.py
+++ b/mesonbuild/modules/windows.py
@@ -107,7 +107,7 @@ class WindowsModule(ExtensionModule):
'a MinGW bug: https://sourceware.org/bugzilla/show_bug.cgi?id=4933'
for arg in extra_args:
if ' ' in arg:
- mlog.warning(m.format(arg))
+ mlog.warning(m.format(arg), fatal=False)
res_targets = []