summaryrefslogtreecommitdiff
path: root/meson_options.txt
Commit message (Collapse)AuthorAgeFilesLines
* edid: Integrate libdisplay-info for edid parsingadarshgm2023-05-021-0/+6
| | | | | | | | | | Hides libdisplay-info under a build time default-off flag, provides provision to parse essential edid parameters with APIs provided by libdisplay-info. This implementaion increases readibility, avoids code duplication and decreases complexity of edid parsing. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2642>
* build: Allow disabling xwaylandBilal Elmoussaoui2023-01-031-0/+6
| | | | | | | | | | Mostly moving things around to allow a build without xwayland. Note that more work might still be needed once the x11 build option lands as that would allow us to have a proper xwayland only build without the x server part. Related: https://gitlab.gnome.org/GNOME/mutter/-/issues/2272 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2399>
* core: Make sound player feature optionalBilal Elmoussaoui2022-09-021-0/+6
| | | | | | | | | | | | | | | | | Mutter can play sounds in some contexts and also provides an API for libmutter users to do so using libcanberra internally. In some specific use cases of Mutter, we would like to not depend on libcanberra and not have any sound playing feature by default. The changes keeps the sound player API but make it no-op if the sound_player feature is disabled to not make it possible to break a gnome-shell build. See https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2270 for relevant discussion Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2375>
* Add 'catch' optionJonas Ådahl2022-08-191-0/+6
| | | | | | | | | | | | | | | The catch option makes test run via 'catch'[1], which will log backtraces whenever an abort or segmentation fault happens in any of the subprocesses. The aim is to enable this when running in CI to help debugging crashes that only tend to happen in CI. While it's possible to wrap the whole meson command in 'catch', doing so doesn't cover the KVM tests, so this option is added instead that covers both cases. [1] https://gitlab.gnome.org/jadahl/catch/ Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2561>
* meson: Allow to build without gnome-desktopBilal Elmoussaoui2022-03-031-0/+6
| | | | | | | | | | gnome-desktop is used to retrieve the monitor vendor name which in some use cases is not needed as it brings a bunch of gnome-desktop unwanted dependencies. The change makes mutter fallback to an "Undefined" vendor name if it is built without gnome-desktop Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2317>
* xwayland: Use Xwayland auto-terminate featureOlivier Fourdan2022-01-261-6/+0
| | | | | | | | | | | | When using Xwayland-on-demand (default), if the (experimental) autoclose features is enabled, we can rely on Xwayland's auto-terminate feature instead of explicitly killing the Xwayland process. With it, gone is the mechanism that was added to check the X11 clients connected and their executable to check whether we can (safely) kill Xwayland. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1794>
* documentation: Generate API references with gi-docgenAndy Holmes2022-01-201-0/+6
| | | | | | | | gtk-doc support was taken out about six years ago, but never replaced. Add support for the newer gi-docgen, which should hopefully encourage both C and GJS users of these libraries to improve the reference. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2248>
* tests: Add ways to run privileged tests without KVMJonas Ådahl2022-01-141-0/+6
| | | | | | | | | These will be skipped by default, but can be run from a TTY for easier debugging by doing: dbus-run-session -- meson test -C build --suite mutter/native/tty --setup plain Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2151>
* tests: Run KMS tests inside a QEMU virtual machineJonas Ådahl2022-01-141-0/+12
| | | | | | | | | | | | | | | | This commit makes it possible to run test executables in a test environment constructed of a virtual machine running the Linux kernel with the virtual KMS driver enabled, and a mocked system environment using meta-dbus-runner.py/python-dbusmock. The qemu machine is configured to use 256M of memory, as the default 128M was not enough for the tests to pass. Using qemu is also only made possible on x86_64; more changes are needed for it to be runnable on aarch64, so add a warning if it was enabled on any other architecture. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2151>
* meson: Add optional libsystemd dependencyNishal Kulkarni2021-09-021-0/+6
| | | | | | | | | | | To utilize the API provided by libsystemd it would be better to create a separate HAVE_LIBSYSTEMD configuration option instead of having to rely on HAVE_NATIVE_BACKEND. For now this will be utilized for getting the control group of a MetaWindow. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1960>
* meson: Add udev_dir optionMichel Dänzer2021-05-041-0/+6
| | | | | | | Same as in gnome-settings-daemon, allows overriding where to install udev rules files. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1844>
* tests: Add headless native backend testJonas Ådahl2021-03-121-0/+6
| | | | | | | | | | It doesn't do anything more than construct and tear down, but it's a start. Don't run the test as part of CI yet, as doesn't have the DRM devices needed. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1698>
* xwayland: Check X11 clients prior to terminate XwaylandOlivier Fourdan2021-01-181-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* *: Fix spelling mistakes found by codespellBjörn Daase2020-08-291-1/+1
| | | | https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1410
* meson_options: Use libGLESv2.so.2 for COGL_DRIVER=gles2, not libGLESv2.soDaniel van Vugt2020-06-091-1/+1
| | | | | | | | | | The former is present on any system that supports OpenGL|ES 2. The latter is just provided in developer packages. Since we access the library via `g_module_open` it's safe to just rely on `libGLESv2.so.2`. Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1282 https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1298
* meson: Expand on xwayland_initfd option descriptionMart Raudsepp2020-03-091-1/+1
| | | | https://gitlab.gnome.org/GNOME/mutter/merge_requests/1104
* wayland: Set up initialization X11 socketCarlos Garnacho2020-02-291-0/+6
| | | | | | | | | | | | | This is used by GDK and the X11 bits, but may also be used for other initialization services we might need to run along with Xwayland initialization. However, as the -initfd argument in Xwayland is a fairly new feature, add some meson build-time checks so that the feature is handled transparently while allowing to explicitly set/unset it. https://gitlab.gnome.org/GNOME/mutter/merge_requests/945
* cogl: Add libsysprof capture based tracingJonas Ådahl2019-05-311-0/+6
| | | | | | | | | | | | | | | | | | | | | | | Add the ability to add tracing instrumentation to the code. When enabled, trace entries will generate a file with timing information that will be processable by sysprof for generating visualization of traces over time. While enabled by default at compile time, it is possible to disable the expansion of the macros completely by passing --disable-tracing to ./configure. Tracing is so far only actually done if actually enabled on explicitly specified threads. This will be used by Mutter passing the write end of a pipe, where the read end is sent to Sysprof itself via the D-Bus method 'Capture()'. By passing that, we have to detect EPIPE that is sent when Sysprof stops recording. Fortunately, we already ignore the signal at meta_init(), so no need to add a custom signal handler. https://gitlab.gnome.org/GNOME/mutter/merge_requests/197
* meson: Add option flags to control test suites buildingMarco Trevisan (Treviño)2019-05-021-1/+7
| | | | | | | Now the `tests` meson option controls weather we should build all the test suites while `core_tests` controls mutter tests. https://gitlab.gnome.org/GNOME/mutter/merge_requests/442
* build: Make libcanberra no longer optionalCarlos Garnacho2019-01-081-6/+0
| | | | | This is not the case anymore with MetaSoundPlayer in place, and also important to get keyboard bell right.
* Add Meson support for installed testsGeorges Basile Stavracas Neto2018-12-201-0/+6
| | | | | | | | | | | | | | | | | | | This is the last remaining feature necessary to achieve parity with the Autotools build. A few changes were made to the install locations of the tests, in order to better acomodate them in Meson: * Tests are now installed under a versioned folder (e.g. /usr/share/installed-tests/mutter-4) * The mutter-cogl.test file is now generated from an .in file, instead of a series of $(echo)s from within Makefile. Notice that those tests need very controlled environments to run correctly. Mutter installed tests, for example, will failed when running under a regular session due to D-Bus failing to acquire the ScreenCast and/or RemoteScreen names.
* Add meson build supportJonas Ådahl2018-11-061-0/+142
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'.
View Lorry Controller Status