I don't think an input thread can ever be useful on Windows.
There is a pthread emulation, so having the thread itself isn't much of a
problem.
However, there is no device to wait on for Windows events, and even if we
were to replace select() with WFMO, Windows wants to send events for a
window to the thread which created that window.
So, force --disable-input-thread
Signed-off-by: Jon Turney <jon.tur...@dronecode.org.uk>
---
configure.ac | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/configure.ac b/configure.ac
index 1f9637a..1614584 100644
--- a/configure.ac
+++ b/configure.ac
@@ -864,6 +864,11 @@ if test "x$HAVE_RECURSIVE_MUTEX" = "xyes" ; then
THREAD_DEFAULT=yes
fi
+case $host_os in
+ mingw*) THREAD_DEFAULT=no ;;
+ *)
+esac
+
AC_ARG_ENABLE(input-thread, AS_HELP_STRING([--enable-input-thread],
[Enable input threads]),
[INPUTTHREAD=$enableval], [INPUTTHREAD=$THREAD_DEFAULT])
--
2.8.3
_______________________________________________
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: https://lists.x.org/mailman/listinfo/xorg-devel
