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
|
|
|
msgfmt = find_program('msgfmt')
|
|
|
|
|
|
|
|
|
|
# Unconditionally use this dir to avoid a circular dep with gnomecc
|
2023-05-04 07:49:59 -04:00
|
|
|
gnome_keybindings_keysdir = datadir / 'gnome-control-center/keybindings'
|
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
|
|
|
|
|
|
|
|
keybinding_xml_files = [
|
|
|
|
|
'50-mutter-navigation.xml',
|
|
|
|
|
'50-mutter-system.xml',
|
|
|
|
|
'50-mutter-windows.xml',
|
|
|
|
|
]
|
|
|
|
|
|
|
|
|
|
if have_wayland
|
|
|
|
|
keybinding_xml_files += [
|
|
|
|
|
'50-mutter-wayland.xml',
|
|
|
|
|
]
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
install_data(keybinding_xml_files,
|
|
|
|
|
install_dir: gnome_keybindings_keysdir,
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
xwayland_grab_default_access_rules = get_option('xwayland_grab_default_access_rules')
|
|
|
|
|
|
|
|
|
|
gschema_config = configuration_data()
|
|
|
|
|
gschema_config.set('GETTEXT_DOMAIN', meson.project_name())
|
|
|
|
|
gschema_config.set('XWAYLAND_GRAB_DEFAULT_ACCESS_RULES',
|
|
|
|
|
xwayland_grab_default_access_rules)
|
|
|
|
|
|
2023-05-04 07:49:59 -04:00
|
|
|
schemadir = datadir / 'glib-2.0' / 'schemas'
|
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
|
|
|
configure_file(
|
|
|
|
|
input: 'org.gnome.mutter.gschema.xml.in',
|
|
|
|
|
output: 'org.gnome.mutter.gschema.xml',
|
|
|
|
|
configuration: gschema_config,
|
|
|
|
|
install_dir: schemadir
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
configure_file(
|
|
|
|
|
input: 'org.gnome.mutter.wayland.gschema.xml.in',
|
|
|
|
|
output: 'org.gnome.mutter.wayland.gschema.xml',
|
|
|
|
|
configuration: gschema_config,
|
|
|
|
|
install_dir: schemadir
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
install_data(['mutter-schemas.convert'],
|
2023-05-04 07:49:59 -04:00
|
|
|
install_dir: datadir / 'GConf/gsettings',
|
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
|
|
|
)
|
2020-09-14 14:36:17 -04:00
|
|
|
|
|
|
|
|
if have_libgudev
|
|
|
|
|
install_data(['61-mutter.rules'],
|
2023-05-04 07:49:59 -04:00
|
|
|
install_dir: udev_dir / 'rules.d',
|
2020-09-14 14:36:17 -04:00
|
|
|
)
|
|
|
|
|
endif
|
2021-07-29 02:44:36 -04:00
|
|
|
|
|
|
|
|
subdir('dbus-interfaces')
|