Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 13:55:35 +00:00
|
|
|
option('opengl',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable OpenGL'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('opengl_libname',
|
|
|
|
|
type: 'string',
|
|
|
|
|
value: 'libGL.so.1',
|
|
|
|
|
description: 'OpenGL library file name'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('gles2_libname',
|
|
|
|
|
type: 'string',
|
2020-06-09 10:25:59 +00:00
|
|
|
value: 'libGLESv2.so.2',
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 13:55:35 +00:00
|
|
|
description: 'GLESv2 library file name'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('gles2',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable GLES2 support'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('egl',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable EGL support'
|
|
|
|
|
)
|
|
|
|
|
option('glx',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable GLX support'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('wayland',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable Wayland support'
|
|
|
|
|
)
|
|
|
|
|
|
2021-08-05 14:07:28 +00:00
|
|
|
option('systemd',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable systemd support'
|
|
|
|
|
)
|
|
|
|
|
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 13:55:35 +00:00
|
|
|
option('native_backend',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable the native backend'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('remote_desktop',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable remote desktop and screen cast support'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('egl_device',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: false,
|
|
|
|
|
description: 'Enable EGLDevice and EGLStream renderer support'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('wayland_eglstream',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: false,
|
|
|
|
|
description: 'Enable Wayland EGLStream support client support'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('udev',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable udev support when using the X11 backend'
|
|
|
|
|
)
|
|
|
|
|
|
2021-04-29 14:33:36 +00:00
|
|
|
option('udev_dir',
|
|
|
|
|
type: 'string',
|
|
|
|
|
value: '',
|
|
|
|
|
description: 'Absolute path of the udev base directory'
|
|
|
|
|
)
|
|
|
|
|
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 13:55:35 +00:00
|
|
|
option('libwacom',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable libwacom support'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('pango_ft2',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable PangoFt2 support'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('startup_notification',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable startup notification support'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('sm',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable X11 session management support'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('introspection',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable GObject introspection'
|
|
|
|
|
)
|
|
|
|
|
|
2022-01-19 20:26:30 +00:00
|
|
|
option('docs',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: false,
|
|
|
|
|
description: 'Enable gi-docgen documentation'
|
|
|
|
|
)
|
|
|
|
|
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 13:55:35 +00:00
|
|
|
option('cogl_tests',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable cogl tests'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('clutter_tests',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable clutter tests'
|
|
|
|
|
)
|
|
|
|
|
|
2019-02-13 17:51:21 +00:00
|
|
|
option('core_tests',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable mutter core tests'
|
|
|
|
|
)
|
|
|
|
|
|
2021-01-19 16:48:04 +00:00
|
|
|
option('native_tests',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable mutter native backend tests'
|
|
|
|
|
)
|
|
|
|
|
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 13:55:35 +00:00
|
|
|
option('tests',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
2019-02-13 17:51:21 +00:00
|
|
|
description: 'Enable tests globally. Specific test suites can be controlled with core_tests, clutter_tests, and cogl_tests'
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 13:55:35 +00:00
|
|
|
)
|
|
|
|
|
|
2021-12-10 22:49:48 +00:00
|
|
|
option('kvm_tests',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: false,
|
|
|
|
|
description: 'Enable running certain tests in a virtual machine with a custom built kernel'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('kvm_kernel_image',
|
|
|
|
|
type: 'string',
|
|
|
|
|
value: '',
|
|
|
|
|
description: 'Path to a Linux kernel image to be used for KVM testing'
|
|
|
|
|
)
|
|
|
|
|
|
2021-12-13 09:39:45 +00:00
|
|
|
option('tty_tests',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: false,
|
|
|
|
|
description: 'Enable tests that must be run on a TTY (KMS tests without KVM)'
|
|
|
|
|
)
|
|
|
|
|
|
2018-05-15 15:31:29 +00:00
|
|
|
option('profiler',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable Sysprof tracing'
|
|
|
|
|
)
|
|
|
|
|
|
2018-12-17 15:26:07 +00:00
|
|
|
option('installed_tests',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable mutter installed tests'
|
|
|
|
|
)
|
|
|
|
|
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 13:55:35 +00:00
|
|
|
option('verbose',
|
|
|
|
|
type: 'boolean',
|
|
|
|
|
value: true,
|
|
|
|
|
description: 'Enable verbose logging ability'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('xwayland_path',
|
|
|
|
|
type: 'string',
|
|
|
|
|
value: '',
|
|
|
|
|
description: 'Path to Xwayland executable'
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
option('xwayland_grab_default_access_rules',
|
|
|
|
|
type: 'string',
|
|
|
|
|
value: 'gnome-boxes,remote-viewer,virt-viewer,virt-manager,vinagre,vncviewer,Xephyr',
|
2020-08-26 09:49:50 +00:00
|
|
|
description: 'Comma delimited list of applications resources or class allowed to issue X11 grabs in Xwayland'
|
Add meson build support
This commit adds meson build support to mutter. It takes a step away
from the three separate code bases with three different autotools setups
into a single meson build system. There are still places that can be
unified better, for example by removing various "config.h" style files
from cogl and clutter, centralizing debug C flags and other configurable
macros, and similar artifacts that are there only because they were once
separate code bases.
There are some differences between the autotools setup and the new
meson. Here are a few:
The meson setup doesn't generate wrapper scripts for various cogl and
clutter test cases. What these tests did was more or less generate a
tiny script that called an executable with a test name as the argument.
To run particular tests, just run the test executable with the name of
the test as the argument.
The meson setup doesn't install test files anymore. The autotools test
suite was designed towards working with installed tests, but it didn't
really still, and now with meson, it doesn't install anything at all,
but instead makes sure that everything runs with the uninstalled input
files, binaries and libraries when running the test suite. Installable
tests may come later.
Tests from cogl, clutter and mutter are run on 'meson test'. In
autotools, only cogl and clutter tests were run on 'make check'.
2018-05-22 13:55:35 +00:00
|
|
|
)
|
2019-07-19 20:50:31 +00:00
|
|
|
|
|
|
|
|
option('xwayland_initfd',
|
|
|
|
|
type: 'feature',
|
|
|
|
|
value: 'auto',
|
2020-03-03 15:40:11 +00:00
|
|
|
description: 'Whether -initfd argument is passed to Xwayland to guarantee services (e.g. gsd-xsettings) startup before applications'
|
2019-07-19 20:50:31 +00:00
|
|
|
)
|
xwayland: Check X11 clients prior to terminate Xwayland
Currently, mutter checks for the presence of X11 windows to decide
whether or not Xwayland can be terminated, when Xwayland is started on
demand.
Unfortunately, not all X11 clients will map a window all the time, an
X11 client may keep the X11 connection opened after closing all its
windows. In that case, we may terminate Xwayland while there are some
X11 client connected still, and terminating Xwayland will also kill
those X11 clients.
To avoid that issue, check the X11 clients actually connected using the
XRes extension. The XRes extension provides the PID of the (local) X11
clients connected to the Xserver, so we need to match that against the
actual executable names, and compare with a list of known executables
that we can safely ignore, such as ibus-x11 or gsd-xsettings.
We also check against our own executable name, considering that the X11
window manager is also an X11 client connected to the Xserver.
Also, XRes returning the PID of local clients only is not a problem
considering that Xwayland does not listen to remote connections.
However, if the user spawns a client remotely on another system using
ssh tunneling (ssh -X), only clients which actually map a window will
be accounted for.
Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1537
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1671>
2021-01-18 09:22:01 +00:00
|
|
|
|
|
|
|
|
option('xwayland_ignore_executables',
|
|
|
|
|
type: 'string',
|
|
|
|
|
value: 'gsd-xsettings,ibus-x11,pulseaudio,Xwayland',
|
|
|
|
|
description: 'Comma delimited list of executable names to ignore when terminating Xwayland'
|
|
|
|
|
)
|