brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
ffa5fd776d
mutter/config.h.meson

94 lines
2.3 KiB
Plaintext
Raw Normal View History

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 09:55:35 -04:00
/* The prefix for our gettext translation domains. */
#mesondefine GETTEXT_PACKAGE
/* Version number of package */
#mesondefine VERSION
/* Version number of package */
#mesondefine PACKAGE_VERSION
/* Search path for plugins */
#mesondefine MUTTER_PLUGIN_DIR
/* */
#mesondefine MUTTER_LOCALEDIR
/* */
#mesondefine MUTTER_LIBEXECDIR
/* */
#mesondefine MUTTER_PKGDATADIR
/* Defined if EGL support is enabled */
#mesondefine HAVE_EGL
/* Defined if EGLDevice support is enabled */
#mesondefine HAVE_EGL_DEVICE
/* Defined if EGLStream support is enabled */
#mesondefine HAVE_WAYLAND_EGLSTREAM
/* Building with gudev for device type detection */
#mesondefine HAVE_LIBGUDEV
/* Building with libwacom for advanced tablet management */
#mesondefine HAVE_LIBWACOM
meson: Add optional libsystemd dependency 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>
2021-08-05 10:07:28 -04:00
/* Building with libsystemd */
#mesondefine HAVE_LIBSYSTEMD
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 09:55:35 -04:00
/* Define if you want to enable the native (KMS) backend based on systemd */
#mesondefine HAVE_NATIVE_BACKEND
/* Define if you want to enable Wayland support */
#mesondefine HAVE_WAYLAND
/* Defined if screen cast and remote desktop support is enabled */
#mesondefine HAVE_REMOTE_DESKTOP
/* Building with SM support */
#mesondefine HAVE_SM
/* Building with startup notification support */
#mesondefine HAVE_STARTUP_NOTIFICATION
*: Fix spelling mistakes found by codespell https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1410
2020-08-26 05:49:50 -04:00
/* Building with Sysprof profiling support */
build: Rename HAVE_TRACING to HAVE_PROFILER in Mutter It fits better the name of the build flag. Cogl still uses HAVE_TRACING since profiler is already used by it. https://gitlab.gnome.org/GNOME/mutter/merge_requests/603
2019-05-31 11:42:27 -04:00
#mesondefine HAVE_PROFILER
cogl: Add libsysprof capture based tracing 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
2018-05-15 11:31:29 -04:00
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 09:55:35 -04:00
/* Path to Xwayland executable */
#mesondefine XWAYLAND_PATH
/* Xwayland applications allowed to issue keyboard grabs */
#mesondefine XWAYLAND_GRAB_DEFAULT_ACCESS_RULES
/* XKB base prefix */
#mesondefine XKB_BASE
main: Make process PR_SET_DUMPABLE Otherwise we won't get core dumps if the launching binary has capabilities set. https://gitlab.gnome.org/GNOME/mutter/merge_requests/811
2019-09-27 04:15:48 -04:00
/* Whether <sys/prctl.h> exists and it defines prctl() */
#mesondefine HAVE_SYS_PRCTL
xwayland: Fix build without <sys/random.h> The include <sys/random.h> was added to glibc-2.25, previously was <linux/random.h>. Adjust meson build and code to accomodate both. Fixes: a8984a81c "xwayland: Generate a Xauth file and pass this to Xwayland when starting it" https://gitlab.gnome.org/GNOME/mutter/merge_requests/633
2019-06-20 06:11:29 -04:00
/* Either <sys/random.h> or <linux/random.h> */
#mesondefine HAVE_SYS_RANDOM
#mesondefine HAVE_LINUX_RANDOM
wayland: Set up initialization X11 socket 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
2019-07-19 16:50:31 -04:00
/* Whether Xwayland has -initfd option */
#mesondefine HAVE_XWAYLAND_INITFD
Add read-only anonymous file abstraction MetaAnonymousFile Add MetaAnonymousFile, an abstraction around anonymous read-only files. Files can be created by calling meta_anonymous_file_new(), passing the data of the file. Subsequent calls to meta_anonymous_file_open_fd() return a fd that's ready to be sent over the socket. When mapmode is META_ANONYMOUS_FILE_MAPMODE_PRIVATE the fd is only guaranteed to be mmap-able readonly with MAP_PRIVATE but does not require duplicating the file for each resource when memfd_create is available. META_ANONYMOUS_FILE_MAPMODE_SHARED may be used when the client must be able to map the file with MAP_SHARED but it also means that the file has to be duplicated even when memfd_create is available. Pretty much all of this code was written for weston by Sebastian Wick, see https://gitlab.freedesktop.org/wayland/weston/merge_requests/240. Co-authored-by: Sebastian Wick <sebastian@sebastianwick.net> https://gitlab.gnome.org/GNOME/mutter/merge_requests/1012
2020-01-17 17:43:24 -05:00
xwayland: Check for listenfd option Current Xwayland has marked the command line option "-listen" as deprecated in favor of "-listenfd". Use the pkg-config variable "have_listenfd" (if available) from Xwayland to determine if we should use that option, to avoid a deprecation warning when spawning Xwayland. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1682>
2021-01-22 05:16:24 -05:00
/* Whether Xwayland has -listenfd option */
#mesondefine HAVE_XWAYLAND_LISTENFD
wayland: Set IO error exit handler If this call is available, we can turn libX11 IO errors (fatal by definition) into something we can recover from. Try to dispose all X11 resources and close the display instead, so the compositor can survive the event. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1447
2019-06-14 10:04:44 -04:00
/* Whether libX11 has XSetIOErrorExitHandler */
#mesondefine HAVE_XSETIOERROREXITHANDLER
Add read-only anonymous file abstraction MetaAnonymousFile Add MetaAnonymousFile, an abstraction around anonymous read-only files. Files can be created by calling meta_anonymous_file_new(), passing the data of the file. Subsequent calls to meta_anonymous_file_open_fd() return a fd that's ready to be sent over the socket. When mapmode is META_ANONYMOUS_FILE_MAPMODE_PRIVATE the fd is only guaranteed to be mmap-able readonly with MAP_PRIVATE but does not require duplicating the file for each resource when memfd_create is available. META_ANONYMOUS_FILE_MAPMODE_SHARED may be used when the client must be able to map the file with MAP_SHARED but it also means that the file has to be duplicated even when memfd_create is available. Pretty much all of this code was written for weston by Sebastian Wick, see https://gitlab.freedesktop.org/wayland/weston/merge_requests/240. Co-authored-by: Sebastian Wick <sebastian@sebastianwick.net> https://gitlab.gnome.org/GNOME/mutter/merge_requests/1012
2020-01-17 17:43:24 -05:00
/* Whether the mkostemp function exists */
#mesondefine HAVE_MKOSTEMP
/* Whether the posix_fallocate function exists */
#mesondefine HAVE_POSIX_FALLOCATE
/* Whether the memfd_create function exists */
#mesondefine HAVE_MEMFD_CREATE
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 04:22:01 -05:00
/* List of executable names to ignore when terminating Xwayland */
#mesondefine XWAYLAND_IGNORE_EXECUTABLES
Reference in New Issue Copy Permalink