summaryrefslogtreecommitdiffstats
path: root/wscript
diff options
context:
space:
mode:
authorDudemanguy <random342@airmail.cc>2022-10-16 09:36:21 -0500
committerDudemanguy <random342@airmail.cc>2022-10-17 14:57:42 +0000
commit48ad2278c7a1fc2a9f5520371188911ef044b32c (patch)
tree169ba7c973611c840a3a59a95290d440ba6db2d5 /wscript
parentcdcbd7372d91d2259d6c1b6b84c65643487e4205 (diff)
downloadmpv-48ad2278c7a1fc2a9f5520371188911ef044b32c.tar.bz2
mpv-48ad2278c7a1fc2a9f5520371188911ef044b32c.tar.xz
wscript: remove some bogus configure options
It turns out that wayland-scanner and wayland-protocols are both exposed as configure options in waf meaning you can --enable/--disable them at configure time. This is pretty nonsensical. If you want to control wayland in the build, you should just use --enable-/--disable-wayland. wayland-scanner and wayland-protocols should just be typical checks like in the meson build.
Diffstat (limited to 'wscript')
-rw-r--r--wscript4
1 files changed, 2 insertions, 2 deletions
diff --git a/wscript b/wscript
index 5d46507d82..851b1a5c7b 100644
--- a/wscript
+++ b/wscript
@@ -516,11 +516,11 @@ video_output_features = [
'deps': 'gbm.h',
'func': check_pkg_config('gbm', '>= 17.1.0'),
} , {
- 'name': '--wayland-scanner',
+ 'name': 'wayland-scanner',
'desc': 'wayland-scanner',
'func': check_program('wayland-scanner', 'WAYSCAN')
} , {
- 'name': '--wayland-protocols',
+ 'name': 'wayland-protocols',
'desc': 'wayland-protocols',
'func': check_wl_protocols
} , {