Fixes deprecation warning for meson 0.56.0 and later.
Raises minimum meson version to 0.56.0.
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Sets minimum meson version to 0.50.0 due to use of:
* 0.49.0: {'/ with string arguments'}
* 0.50.0: {'install arg in configure_file'}
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
We could not find any evidence it was ever used, but defining it
caused C++11 compilers to complain:
/usr/X11R6/include/X11/Xfuncproto.h:173:24:
warning: ISO C does not permit named variadic macros [-Wvariadic-macros]
#define _X_NONNULL(args...) __attribute__((nonnull(args)))
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
The actual protocol and implementation details are unaffected - both
here and in xcb. Only the description/diagram section is off.
Noticed while skimming through the new 1.3 additions.
Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
This extension exists to serve one purpose: reliably identifying
Xwayland. Previous attempts at doing so included querying root window
properties, output names or input device names. All these attempts are
somewhat unreliable. Instead, let's use an extension - where that
extension is present we have an Xwayland server.
Clients should never need to do anything but check whether the extension
exists through XQueryExtension/XListExtensions.
This extension provides a single QueryVersion request only, and
that is only to provide future compatibility if we ever need anything
other than "this extension exists" functionality.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Olivier Fourdan <ofourdan@redhat.com>
Workaround the collision between ControlMask #defined in X11/X.h and
ControlMask used as the name of a structure member in
w32api/processthreadsapi.h in w32api 10.0.0
DRI3SetDRMDeviceInUse is a hint that lets a client tell the server
what DRM device it is currently using. This lets the server make
more informed decisions for what modifiers to return to the client.
This is needed for proper linux dmabuf feedback with Xwayland
All modern compilers (GCC>=4.6, Clang>=3.0) define this macro, so we can
use it to detect 64-bit longs without adding to the architecture list.
This change allows me to successfully run a simple X11 window on a
64-bit FreeBSD RISC-V QEMU VM via SSH forwarding. Without this change
I get an error that DISPLAY cannot be opened.
Signed-off-by: Alex Richardson <Alexander.Richardson@cl.cam.ac.uk>
The Xserver itself is capable of terminating itself once all X11 clients
are gone, yet in a typical full session, there are a number of X11
clients running continuously (e.g. the Xsettings daemon, IBus, etc.).
Those always-running clients will prevent the Xserver from terminating,
because the actual number of X11 clients will never drop to 0.
To solve this issue directly at the Xserver level, this add new entries
to the XFixes extension to let the X11 clients themselves specify the
disconnect mode they expect.
Typically, those X11 daemon clients would specify the disconnect mode
XFixesClientDisconnectFlagTerminate to let the Xserver know that they
should not be accounted for when checking the remaining clients prior
to terminate.
Signed-off-by: Olivier Fourdan <ofourdan@redhat.com>
Build and install with meson, build and install with autotools and then run
diff to compare the two directory trees. They should be the same.
This does not install the legacy protocols, they're behind a configure switch.
The spec-build is disabled in autotools because we know meson doesn't do that
yet, so no point in comparing those.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
autotools can't pass arguments, so let's default to 'verify' in the script
itself and for distcheck to succeed, we need to set an environment variable to
search for the header (it's an out-of-tree build).
And due to the very faint chance of there being no python during the
xorgproto build, let's make that conditional too.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
An alphabetically ordered list is nice, but it's harder to figure out
based on a diff whether a commit affects the legacy protocols or not.
Let's group those separately, first the normal protocol files, then all the
legacy-only ones.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
