summaryrefslogtreecommitdiff
path: root/meson_options.txt
Commit message (Collapse)AuthorAgeFilesLines
* *: 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'.