isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-28 11:00:54 -05:00
Code Issues Packages Projects Releases Wiki Activity
60781bc6c2
mutter/src/Makefile.am

743 lines
24 KiB
Makefile
Raw Normal View History

Add .AUTOPARALLEL flag to Makefile This automatically enables parallelism with the patched make, and flags us as maintaining a parallel build.
2009-08-30 20:21:02 -04:00
# Flag build for parallelism; see https://savannah.gnu.org/patch/?6905
.AUTOPARALLEL:
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
lib_LTLIBRARIES = libmutter-@LIBMUTTER_API_VERSION@.la
...
2001-06-02 00:14:18 -04:00
Remove old, deprecated utilities that nobody has used in a million years https://bugzilla.gnome.org/show_bug.cgi?id=704437
2013-07-17 23:15:02 -04:00
SUBDIRS=compositor/plugins
Basic plugin infastructure and a sample simple plugin.
2008-09-18 11:09:11 -04:00
Add a test framework and stacking tests Add a basic framework for tests of Mutter handling of client behavior; mutter-test-runner is a Mutter-based compositor that forks off instances of mutter-test-client and sends commands to them based on scripts. The scripts also include assertions. mutter-test-runner always runs in nested-Wayland mode since the separate copy of Xwayland is helpful in giving a reliably clean X server to test against. Initially the commands and assertions are designed to test the stacking behavior of Mutter, but the framework should be extensible to test other parts of client behavior like focus. The tests are installed according to: https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests if --enable-installed-tests is passed to configure. You can run them uninstalled with: cd src && make run-tests (Not in 'make check' to avoid breaking 'make distcheck' if Mutter can't be run nested.) https://bugzilla.gnome.org/show_bug.cgi?id=736505
2014-09-11 13:43:32 -04:00
EXTRA_DIST =
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
NULL =
Add a test framework and stacking tests Add a basic framework for tests of Mutter handling of client behavior; mutter-test-runner is a Mutter-based compositor that forks off instances of mutter-test-client and sends commands to them based on scripts. The scripts also include assertions. mutter-test-runner always runs in nested-Wayland mode since the separate copy of Xwayland is helpful in giving a reliably clean X server to test against. Initially the commands and assertions are designed to test the stacking behavior of Mutter, but the framework should be extensible to test other parts of client behavior like focus. The tests are installed according to: https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests if --enable-installed-tests is passed to configure. You can run them uninstalled with: cd src && make run-tests (Not in 'make check' to avoid breaking 'make distcheck' if Mutter can't be run nested.) https://bugzilla.gnome.org/show_bug.cgi?id=736505
2014-09-11 13:43:32 -04:00
build: Fix some warnings and clean up a bit
2014-06-04 13:31:37 -04:00
AM_CPPFLAGS = \
build: Define CLUTTER_ENABLE_COMPOSITOR_API
2014-02-24 08:35:06 -05:00
-DCLUTTER_ENABLE_COMPOSITOR_API \
Enable CLUTTER / COGL_ENABLE_EXPERIMENTAL_API globally Instead of defining CLUTTER_ENABLE_EXPERIMENTAL_API and COGL_ENABLE_EXPERIMENTAL_API in individual source files, enable them on the command line. We weren't tracking exactly what pieces of experimental API we were using and we were using the experimental API in most source files that used Clutter and Cogl, so the local #defines were annoying rather than useful. https://bugzilla.gnome.org/show_bug.cgi?id=685463
2012-11-12 13:32:30 -05:00
-DCLUTTER_ENABLE_EXPERIMENTAL_API \
-DCOGL_ENABLE_EXPERIMENTAL_API \
compositor: rework how backgrounds are managed Background handling in GNOME is very roundabout at the moment. gnome-settings-daemon uses gnome-desktop to read the background from disk into a screen-sized pixmap. It then sets the XID of that pixmap on the _XROOTPMAP_ID root window property. mutter puts that pixmap into a texture/actor which gnome-shell then uses. Having the gnome-settings-daemon detour from disk to screen means we can't easily let the compositor handle transition effects when switching backgrounds. Also, having the background actor be per-screen instead of per-monitor means we may have oversized textures in certain multihead setups. This commit changes mutter to read backgrounds from disk itself, and it changes backgrounds to be per-monitor. This way background handling/compositing is left to the compositor. https://bugzilla.gnome.org/show_bug.cgi?id=682427
2013-01-23 15:54:41 -05:00
-DCOGL_ENABLE_EXPERIMENTAL_2_0_API \
Create cogl renderer in MetaRenderer Instead of passing around the KMS file descriptor via clutter to cogl, just make our own clutter backend create the cogl renderer and set the KSM fd. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-08 21:59:54 -04:00
-DCOGL_ENABLE_MUTTER_API \
Makefile: Disable Clutter / Cogl deprecation warnings These just spam up our logs, and they aren't getting fixed any time soon for a variety of reasons. Just disable them to ensure that really important warnings get noticed and fixed.
2014-07-13 11:46:13 -04:00
-DCLUTTER_DISABLE_DEPRECATION_WARNINGS \
-DCOGL_DISABLE_DEPRECATION_WARNINGS \
Allow mutter to be used as a library Move all of the mutter code into a new libmutter-wm.so, split its main() method into meta_get_option_context(), meta_init() and meta_run(), add methods for using in-process plugins, and add libmutter-wm.pc pointing to the new library. The mutter binary is now just a tiny program that links against libmutter-wm. The --version and --mutter-plugins options are handled at the mutter level, not in libmutter-wm, and a few strange unused command-line options (--no-force-fullscreen and --no-tab-popup) have been removed. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 16:16:26 -05:00
$(MUTTER_CFLAGS) \
Make the native backend build-optional
2014-05-29 12:11:26 -04:00
$(MUTTER_NATIVE_BACKEND_CFLAGS) \
meta: Add generated meta-version.h Avoid populating *_VERSION constants through cflags in pkg-config-file which could be overridden by the project using it. Properly prefix the defines with META_ to make gi-scanner happy.
2014-06-05 08:05:16 -04:00
-I$(builddir) \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
-I$(srcdir) \
Start molding out a new src/backends/ dir Right now this just has all of the files in one directory. We'll be introducing more structure to this in the future, and build a proper backend system.
2014-03-31 22:07:49 -04:00
-I$(srcdir)/backends \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
-I$(srcdir)/core \
-I$(srcdir)/ui \
Allow mutter to be used as a library Move all of the mutter code into a new libmutter-wm.so, split its main() method into meta_get_option_context(), meta_init() and meta_run(), add methods for using in-process plugins, and add libmutter-wm.pc pointing to the new library. The mutter binary is now just a tiny program that links against libmutter-wm. The --version and --mutter-plugins options are handled at the mutter level, not in libmutter-wm, and a few strange unused command-line options (--no-force-fullscreen and --no-tab-popup) have been removed. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 16:16:26 -05:00
-I$(srcdir)/compositor \
Fix the merged build https://bugzilla.gnome.org/show_bug.cgi?id=760439
2016-04-08 13:58:20 -04:00
-I$(top_srcdir)/cogl \
Make it possible to include private cogl API from mutter If we want to put a cogl winsys backend in mutter, that backend need to have access to the internal workings of cogl. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-06 04:08:30 -04:00
-I$(top_srcdir)/cogl/cogl \
-I$(top_srcdir)/cogl/cogl/winsys \
Fix out-of-tree building We included generated cogl headers and non-generated clutter headers from mutter, while only having added include paths for the opposite.
2016-07-20 04:17:22 -04:00
-I$(top_builddir)/cogl/cogl \
Fix the merged build https://bugzilla.gnome.org/show_bug.cgi?id=760439
2016-04-08 13:58:20 -04:00
-I$(top_builddir)/cogl \
-I$(top_srcdir)/clutter \
Fix out-of-tree building We included generated cogl headers and non-generated clutter headers from mutter, while only having added include paths for the opposite.
2016-07-20 04:17:22 -04:00
-I$(top_srcdir)/clutter/clutter \
Fix the merged build https://bugzilla.gnome.org/show_bug.cgi?id=760439
2016-04-08 13:58:20 -04:00
-I$(top_builddir)/clutter \
-I$(top_builddir)/clutter/clutter \
Allow mutter to be used as a library Move all of the mutter code into a new libmutter-wm.so, split its main() method into meta_get_option_context(), meta_init() and meta_run(), add methods for using in-process plugins, and add libmutter-wm.pc pointing to the new library. The mutter binary is now just a tiny program that links against libmutter-wm. The --version and --mutter-plugins options are handled at the mutter level, not in libmutter-wm, and a few strange unused command-line options (--no-force-fullscreen and --no-tab-popup) have been removed. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 16:16:26 -05:00
-DMUTTER_LIBEXECDIR=\"$(libexecdir)\" \
build: Fix some warnings and clean up a bit
2014-06-04 13:31:37 -04:00
-DMUTTER_LOCALEDIR=\"$(localedir)\" \
Allow mutter to be used as a library Move all of the mutter code into a new libmutter-wm.so, split its main() method into meta_get_option_context(), meta_init() and meta_run(), add methods for using in-process plugins, and add libmutter-wm.pc pointing to the new library. The mutter binary is now just a tiny program that links against libmutter-wm. The --version and --mutter-plugins options are handled at the mutter level, not in libmutter-wm, and a few strange unused command-line options (--no-force-fullscreen and --no-tab-popup) have been removed. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 16:16:26 -05:00
-DMUTTER_PKGDATADIR=\"$(pkgdatadir)\" \
-DMUTTER_DATADIR=\"$(datadir)\" \
-DG_LOG_DOMAIN=\"mutter\" \
-DSN_API_NOT_YET_FROZEN=1 \
-DMUTTER_PKGLIBDIR=\"$(pkglibdir)\" \
build: Fix some warnings and clean up a bit
2014-06-04 13:31:37 -04:00
-DMUTTER_PLUGIN_DIR=\"$(MUTTER_PLUGIN_DIR)\" \
Don't include wayland/ by default either
2014-03-18 22:01:31 -04:00
-DGETTEXT_PACKAGE=\"$(GETTEXT_PACKAGE)\" \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
-DXWAYLAND_PATH=\"$(XWAYLAND_PATH)\" \
$(NULL)
configure: Adds --with-xwayland-path option This adds a --with-xwayland-path configure option that can be used to specify the absolute path of a headless X server binary supporting the wayland xserver protocol.
2012-01-10 13:28:15 -05:00
Emit signals when workspaces are added, removed or switched The patch adds GLib marshalling code to Mutter, since it's required for the "workspace-switched" signal. The definition of MetaMotionDirection enum is moved to common.h since it's now used in workspace.c. A little cleaning is done in workspace.c:meta_workspace_activate_with_focus(), where compositor-specific code is merged with the rest of the function (required to emit signal), removing #ifdefs.
2009-07-02 11:19:02 -04:00
mutter_built_sources = \
build: make wayland support unconditional In the wayland branch of mutter, we want to build a wayland version of the mutter libraries, and that's much easier if we just build wayland support unconditionally. The define is kept to avoid a huge diff, but should be removed in a later patch. Also, wayland support can still be disable at runtime, by launching mutter without the --nested switch. https://bugzilla.gnome.org/show_bug.cgi?id=705497
2013-08-16 07:49:03 -04:00
$(dbus_idle_built_sources) \
Remove "xrandr" from the name of the generated DBus files It's about generic display config, not XRandR specifically.
2014-03-31 23:33:01 -04:00
$(dbus_display_config_built_sources) \
launcher: Replace mutter-launch with logind integration This uses David Herrmann's new logind sessions interface to retrieve fds for input devices, rather than using a custom setuid helper to do the management. This vastly simplifies the interface. This requires systemd v210, at least. https://bugzilla.gnome.org/show_bug.cgi?id=724604
2013-12-31 17:44:45 -05:00
$(dbus_login1_built_sources) \
Install enum types
2015-07-06 00:58:45 -04:00
meta/meta-enum-types.h \
meta-enum-types.c \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
$(NULL)
Only build Wayland protocols when we have Wayland
2014-08-27 12:05:51 -04:00
Add remote desktop and screen cast functionality This commit adds basic screen casting and remote desktoping functionalty. This works by exposing two D-Bus API services: org.gnome.Mutter.ScreenCast and org.gnome.Mutter.RemoteDesktop. The remote desktop API is used to create remote desktop sessions. For each session, a D-Bus object is created, and an application can manage the session by sending messages to the session object. A remote desktop session the user to emit input events using the D-Bus methods on the session object. To get framebuffer content, the application should create an associated screen cast session. The screen cast API is used to create screen cast sessions. One can so far either create stand-alone screen cast sessions, or a screen cast session associated with a remote desktop session. A remote desktop associated screen cast session is managed by the remote desktop session. So far only remote desktop managed screen cast sessions are implemented. Each screen cast session may have one or more streams. A screen cast stream is a stream of buffers of some part of the compositor content. So far API exists for creating streams of monitors and windows, but only monitor streams are implemented. When a screen cast session is started, the one PipeWire stream is created for each screen cast stream created for the session. When this has happened, a PipeWireStreamAdded signal is emitted on the stream object, passing a unique identifier. The application may use this identifier to find the associated stream being advertised by the PipeWire daemon. The remote desktop and screen cast functionality must be explicitly be enabled at ./configure time by passing --enable-remote-desktop to ./configure. Doing this will build both screen cast and remote desktop support. To actually enable the screen casting and remote desktop, the user must enable the experimental feature. See org.gnome.mutter.experimental-features. https://bugzilla.gnome.org/show_bug.cgi?id=784199
2017-06-21 02:23:44 -04:00
if HAVE_REMOTE_DESKTOP
mutter_built_sources += \
$(dbus_remote_desktop_built_sources) \
$(dbus_screen_cast_built_sources) \
$(NULL)
endif
Only build Wayland protocols when we have Wayland
2014-08-27 12:05:51 -04:00
if HAVE_WAYLAND
mutter_built_sources += \
wayland: Use pointer gestures protocol from wayand-protocols Remove our own copy of the pointer gestures protocol, and us the one installed by wayland-protocols. This also means the new fixed unstable naming conventions are used for the new version of the protocol, which is reflected in the change. No functional changes were made, it is only a rename. https://bugzilla.gnome.org/show_bug.cgi?id=758633
2015-11-09 02:28:14 -05:00
pointer-gestures-unstable-v1-protocol.c \
pointer-gestures-unstable-v1-server-protocol.h \
Don't generate sources in a subdirectory This fixes srcdir != builddir issues.
2014-03-18 22:06:20 -04:00
gtk-shell-protocol.c \
gtk-shell-server-protocol.h \
wayland: Add gtk-primary-selection protocol This protocol is an internal mirror of the primary selection drafts being proposed for wayland-protocols. No changes besides prefix/suffix changes. https://bugzilla.gnome.org/show_bug.cgi?id=762560
2016-02-23 13:51:10 -05:00
gtk-primary-selection-protocol.c \
gtk-primary-selection-server-protocol.h \
wayland/xdg-shell: Port to unstable v6 Port the xdg_shell implementation to use the unstable v6 protocol. This includes: - making xdg_surface a generic base interface for xdg_shell surface roles - create a xdg_toplevel role replacing the old xdg_surface - change the xdg_opup role to be based on xdg_surface - make xdg_popup not grab by default - add support for xdg_positioner https://bugzilla.gnome.org/show_bug.cgi?id=769936
2016-07-01 04:30:14 -04:00
xdg-shell-unstable-v6-protocol.c \
xdg-shell-unstable-v6-server-protocol.h \
wayland: Implement support for wp_relative_pointer Add support for sending relative pointer motion deltas to clients who request such events by creating wp_relative_pointer objects via wp_relative_pointer_manager. This currently implements the unstable version 1 from wayland-protocols. https://bugzilla.gnome.org/show_bug.cgi?id=744104
2015-06-02 04:26:34 -04:00
relative-pointer-unstable-v1-protocol.c \
relative-pointer-unstable-v1-server-protocol.h \
Implement support for the wp_pointer_constraints protocol The wp_pointer_constraints protocol is a protocol which enables clients to manipulate the behavior of the pointer cursor associated with a seat. Currently available constraints are locking the pointer to a static position, and confining the pointer to a given region. Currently locking is fully implemented, and confining is implemented for rectangular confinement regions. What else is lacking is less troublesome semantics for enabling the lock or confinement; currently the only requirement implemented is that the window that appears focused is the one that may aquire the lock. This means that a pointer could be 'stolen' by creating a new window that receives active focus, or when using focus-follows-mouse, a pointer passes a window that has requested a lock. This semantics can be changed and the protocol itself allows any semantics as seems fit. https://bugzilla.gnome.org/show_bug.cgi?id=744104
2015-06-17 00:10:52 -04:00
pointer-constraints-unstable-v1-protocol.c \
pointer-constraints-unstable-v1-server-protocol.h \
wayland: Use tablet protocol v2 This commit merely updates the code generation from the v2 protocol description.
2016-05-12 08:32:01 -04:00
tablet-unstable-v2-protocol.c \
tablet-unstable-v2-server-protocol.h \
wayland: Add support for the xdg-foreign protocol This commits adds support for exporting xdg_surface handles via xdg_exporter and importing them via xdg_importer. This bumps the required wayland-protocols version to 1.6. https://bugzilla.gnome.org/show_bug.cgi?id=769786
2015-09-23 20:05:25 -04:00
xdg-foreign-unstable-v1-protocol.c \
xdg-foreign-unstable-v1-server-protocol.h \
wayland: Add zwp_linux_dmabuf_v1 support https://bugzilla.gnome.org/show_bug.cgi?id=785262 Signed-off-by: Daniel Stone <daniels@collabora.com>
2017-07-11 11:03:26 -04:00
linux-dmabuf-unstable-v1-protocol.c \
linux-dmabuf-unstable-v1-server-protocol.h \
wayland: add keyboard shortcuts inhibitor protocol https://bugzilla.gnome.org/show_bug.cgi?id=783342
2017-03-21 06:47:16 -04:00
keyboard-shortcuts-inhibit-unstable-v1-protocol.c \
keyboard-shortcuts-inhibit-unstable-v1-server-protocol.h \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
$(NULL)
Only build Wayland protocols when we have Wayland
2014-08-27 12:05:51 -04:00
endif
wayland: Adds basic hybrid X + Wayland support This adds support for running mutter as a hybrid X and Wayland compositor. It runs a headless XWayland server for X applications that presents wayland surfaces back to mutter which mutter can then composite. This aims to not break Mutter's existing support for the traditional X compositing model which means a single build of Mutter can be distributed supporting the traditional model and the new Wayland based compositing model. TODO: although building with --disable-wayland has at least been tested, I still haven't actually verified that running as a traditional compositor isn't broken currently. Note: At this point no input is supported Note: multiple authors have contributed to this patch: Authored-by: Robert Bragg <robert@linux.intel.com> Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Rico Tzschichholz. Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2012-01-07 17:21:32 -05:00
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
wayland_protocols = \
Move Wayland protocols into src/wayland
2014-03-18 20:32:02 -04:00
wayland/protocol/gtk-shell.xml \
wayland: Add gtk-primary-selection protocol This protocol is an internal mirror of the primary selection drafts being proposed for wayland-protocols. No changes besides prefix/suffix changes. https://bugzilla.gnome.org/show_bug.cgi?id=762560
2016-02-23 13:51:10 -05:00
wayland/protocol/gtk-primary-selection.xml \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
$(NULL)
Move Wayland protocols into src/wayland
2014-03-18 20:32:02 -04:00
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
libmutter_@LIBMUTTER_API_VERSION@_la_SOURCES = \
Move meta_clutter_init into a new file We'll use this to get the initialization between the Wayland and X11 compositor codepaths back in sync.
2014-03-31 23:00:07 -04:00
backends/meta-backend.c \
backends: Make MetaBackend available to introspection This moves meta-backend.h under meta/ and, for now, just exposes to introspection the methods that we actually need in gnome-shell. https://bugzilla.gnome.org/show_bug.cgi?id=734301
2014-08-05 08:11:59 -04:00
meta/meta-backend.h \
backend: Move settings into a new MetaSettings object Introduce MetaSettings and add the settings managed by MetaBackend into the new object. These settings include: experimental-features and UI scaling factor. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-04-21 04:40:51 -04:00
meta/meta-settings.h \
backends: Start on an initial MetaBackend object This isn't great so far -- all we did is put the idle monitors here instead. We'll soon have separate backend subclasses for the two backends.
2014-04-21 19:03:22 -04:00
backends/meta-backend-private.h \
barriers: Separate implementation from public API This patch removes the X11 specific code from MetaBarrier and creates an abstraction layer MetaBarrierImpl. The existing X11 implementation is moved to a new GObject MetaBarrierImplX11 implementing the abstract interface MetaBarrierImpl which is instantiated by MetaBarrier when supported. While at it, move it to backends/ and properly name the files. https://bugzilla.gnome.org/show_bug.cgi?id=706655
2015-01-15 21:30:04 -05:00
backends/meta-barrier.c \
backends/meta-barrier-private.h \
monitor-manager: Make MetaCrtc a GObject Turn MetaCrtc into a GObject and move it to a separate file. This changes the storage format, resulting in changing the API for accessing MetaCrtcs from using an array, to using a GList. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-03-28 00:35:19 -04:00
backends/meta-crtc.c \
backends/meta-crtc.h \
Start molding out a new src/backends/ dir Right now this just has all of the files in one directory. We'll be introducing more structure to this in the future, and build a proper backend system.
2014-03-31 22:07:49 -04:00
backends/meta-cursor.c \
backends/meta-cursor.h \
backends/meta-cursor-tracker.c \
backends/meta-cursor-tracker-private.h \
Split out the code that renders the code into a MetaCursorRenderer Right now, this is the same exact same mess it's always been, but it will be fixed up soon with backend-specific renderers.
2014-04-21 18:05:59 -04:00
backends/meta-cursor-renderer.c \
backends/meta-cursor-renderer.h \
build: Include missing file
2017-03-13 21:59:53 -04:00
backends/meta-dnd-private.h \
Add EGL abstraction class MetaEgl Add a MetaEgl meant to deal with EGL. It is intended to be use by EGL based renderers and handle extension symbols loading, handle errors etc. https://bugzilla.gnome.org/show_bug.cgi?id=773629
2016-08-17 22:18:28 -04:00
backends/meta-egl.c \
build: Fix typo
2016-11-23 15:58:13 -05:00
backends/meta-egl.h \
build: Add missing file
2016-11-23 16:20:32 -05:00
backends/meta-egl-ext.h \
backends: Add OpenGL ES 3 abstraction layer Add helper functions and macros for managing and drawing OpenGL ES 3. It will be used for blitting framebuffers between multiple GPUs in hybrid GPU systems. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-07-24 05:24:29 -04:00
backends/meta-gles3.c \
backends/meta-gles3.h \
backends/meta-gles3-table.h \
backends: Split out CRTC/output management to MetaGpu In order to eventually support multilpe GPUs with their own connectors, split out related meta data management (i.e. outputs, CRTCs and CRTC modes) into a new MetaGpu GObject. The Xrandr backend always assumes there is always only a single "GPU" as the GPU is abstracted by the X server; only the native backend (aside from the test backend) will eventually see more than one GPU. The Xrandr backend still moves some management to MetaGpuXrandr, in order to behave more similarly to the KMS counterparts. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-07-10 06:19:32 -04:00
backends/meta-gpu.c \
backends/meta-gpu.h \
build: Complete rename of header file Fallout from commit d5552cc372405d0.
2014-04-15 16:21:12 -04:00
backends/meta-display-config-shared.h \
Start molding out a new src/backends/ dir Right now this just has all of the files in one directory. We'll be introducing more structure to this in the future, and build a proper backend system.
2014-03-31 22:07:49 -04:00
backends/meta-idle-monitor.c \
backends/meta-idle-monitor-private.h \
backends/meta-idle-monitor-dbus.c \
backends/meta-idle-monitor-dbus.h \
backends: Add MetaInputSettings This object internally keeps track of the relevant input configuration, and goes through its vmethods in order to apply the configuration on the backend-specific devices. So far, only mouse/touchpad settings are actually attached to GSettings changes. ::set_matrix(), meant for tablets/touchscreens, is not hooked yet. One caveat is that meta_input_settings_create() may return NULL if the backend does not own the windowing system (wayland nested on X11 being the one case), and thus device settings can't be changed freely. https://bugzilla.gnome.org/show_bug.cgi?id=739397
2014-10-29 10:30:52 -04:00
backends/meta-input-settings.c \
backends/meta-input-settings-private.h \
monitor-manager: Move logical monitor into its own file https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:37:11 -05:00
backends/meta-logical-monitor.c \
backends/meta-logical-monitor.h \
Introduce new monitor configuration system The new monitor configuration system (MetaMonitorConfigManager) aims to replace the current MetaMonitorConfig. The main difference between the two is that MetaMonitorConfigManager works with higher level input (MetaMonitor, MetaMonitorMode) instead of directly looking at the CRTC and connector state. It still produces CRTC and connector configuration later applied by the respective backends. Other difference the new system aims to introduce is that the configuration system doesn't manipulate the monitor manager state; that responsibility is left for the monitor manager to handle (it only manages configuration and creates CRTC/connector assignments, it doesn't apply anything). The new configuration system allows backends to not rely on deriving the current configuration from the CRTC/connector state, as this may no longer be possible (i.e. when using KMS and multiple framebuffers). The MetaMonitorConfigManager system is so far disabled by default, as it does not yet have all the features of the old system, but eventually it will replace MetaMonitorConfig which will at that point be removed. This will make it possible to remove old hacks introduced due to limitations in the old system. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-09 01:31:18 -05:00
backends/meta-monitor-config-manager.c \
backends/meta-monitor-config-manager.h \
Migrate old monitor configuration files to new system This commit changes the new configuration system to use monitors.xml instead of monitors-experimental.xml. When starting up and the monitors.xml file is loaded, if a legacy monitors.xml file is discovered (it has the version number 1), an attempt is made to migrate the stored configuration onto the new system. This is done in two steps: 1) Parsing and translation of the old configuration. This works by parsing file using the mostly the old parser, but then translating the resulting configuration structs into the new configuration system. As the legacy configuration system doesn't carry over some state (such as tiling and scale used), some things are not available. For tiling, the migration paths makes an attempt to discover tiled monitors by comparing EDID data, and guessing what the main tile is. Determination of the scale of a migrated configuration is postponed until the configuration is actually applied. This works by flagging the configuration as 'migrated'. 2) Finishing the migration when applying. When a configuration with the 'migrated' flag is retrieved from the configuration store, the final step of the migration is taken place. This involves calculating the preferred scale given the mode configured, while making sure this doesn't result in any overlapping logical monitor regions etc. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-08-10 03:12:41 -04:00
backends/meta-monitor-config-migration.c \
backends/meta-monitor-config-migration.h \
Introduce MetaMonitorConfigStore MetaMonitorConfigStore provides an XML storage mechanism for MetaMonitorConfigManager. It stores configuration files defined in the same level as the MetaMonitorsConfig format, i.e. refers to high level "monitors" and "monitor modes" instead of connectors and CRTCs. Only reading custom files are implemented and so far unused. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-01-12 03:13:48 -05:00
backends/meta-monitor-config-store.c \
backends/meta-monitor-config-store.h \
monitor-manager: Generate a monitor abstraction from outputs and crtcs Generate a set of "monitors" abstracting the physical concepts. Each monitor is built up of one or more outputs; multiple outputs being tiled monitors. Logical monitors will later be built from these. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2016-12-12 21:53:38 -05:00
backends/meta-monitor.c \
backends/meta-monitor.h \
Start molding out a new src/backends/ dir Right now this just has all of the files in one directory. We'll be introducing more structure to this in the future, and build a proper backend system.
2014-03-31 22:07:49 -04:00
backends/meta-monitor-manager.c \
monitor-manager: Expose MetaMonitorManager to introspection This just exposes the type and the singleton getter necessary to make it available to introspection. We'll expose more functionality as it becomes needed. https://bugzilla.gnome.org/show_bug.cgi?id=743745
2015-01-30 08:51:18 -05:00
meta/meta-monitor-manager.h \
backends/meta-monitor-manager-private.h \
Start molding out a new src/backends/ dir Right now this just has all of the files in one directory. We'll be introducing more structure to this in the future, and build a proper backend system.
2014-03-31 22:07:49 -04:00
backends/meta-monitor-manager-dummy.c \
backends/meta-monitor-manager-dummy.h \
backends: Add a MetaOrientationManager class This basically moves g-s-d's orientation plugin into mutter so that eventually g-s-d doesn't need to build monitor configurations by itself anymore. https://bugzilla.gnome.org/show_bug.cgi?id=781906
2017-04-28 11:49:00 -04:00
backends/meta-orientation-manager.c \
backends/meta-orientation-manager.h \
Make MetaOutput a GObject Turn MetaOutput into a GObject and move it to a separate file. This changes the storage format, resulting in changing the API for accessing MetaOutputs from using an array, to using a GList. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-03-24 05:35:51 -04:00
backends/meta-output.c \
backends/meta-output.h \
Implement support for the wp_pointer_constraints protocol The wp_pointer_constraints protocol is a protocol which enables clients to manipulate the behavior of the pointer cursor associated with a seat. Currently available constraints are locking the pointer to a static position, and confining the pointer to a given region. Currently locking is fully implemented, and confining is implemented for rectangular confinement regions. What else is lacking is less troublesome semantics for enabling the lock or confinement; currently the only requirement implemented is that the window that appears focused is the one that may aquire the lock. This means that a pointer could be 'stolen' by creating a new window that receives active focus, or when using focus-follows-mouse, a pointer passes a window that has requested a lock. This semantics can be changed and the protocol itself allows any semantics as seems fit. https://bugzilla.gnome.org/show_bug.cgi?id=744104
2015-06-17 00:10:52 -04:00
backends/meta-pointer-constraint.c \
backends/meta-pointer-constraint.h \
backend: Move settings into a new MetaSettings object Introduce MetaSettings and add the settings managed by MetaBackend into the new object. These settings include: experimental-features and UI scaling factor. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-04-21 04:40:51 -04:00
backends/meta-settings.c \
backends/meta-settings-private.h \
backend: Create the stage in the backend, rather than the compositor This allows creating the stage much earlier than it otherwise would have been. Our initialization sequence has always been a bit haphazard, with first the MetaBackend created, then the MetaDisplay, and inside of that, the MetaScreen and MetaCompositor. Refactor this out so that the MetaBackend creates the Clutter stage. Besides the clarity of early initialization, we now have much easier access to the stage, allowing us to use it for things such as key focus and beyond.
2014-08-13 19:46:32 -04:00
backends/meta-stage.h \
backends/meta-stage.c \
Introduce MetaRenderer MetaRenderer is meant to be the object responsible for rendering the scene graph. It will contain the logic related to the cogl winsys backend, the clutter backend, and the clutter stage window. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-07 11:07:46 -04:00
backends/meta-renderer.c \
backends/meta-renderer.h \
Introduce regional stage rendering Add support for drawing a stage using multiple framebuffers each making up one part of the stage. This works by the stage backend (ClutterStageWindow) providing a list of views which will be for splitting up the stage in different regions. A view layout, for now, is a set of rectangles. The stage window (i.e. stage "backend" will use this information when drawing a frame, using one framebuffer for each view. The scene graph is adapted to explictly take a view when painting the stage. It will use this view, its assigned framebuffer and layout to offset and clip the drawing accordingly. This effectively removes any notion of "stage framebuffer", since each stage now may consist of multiple framebuffers. Therefore, API involving this has been deprecated and made no-ops; namely clutter_stage_ensure_context(). Callers are now assumed to either always use a framebuffer reference explicitly, or push/pop the framebuffer of a given view where the code has not yet changed to use the explicit-buffer-using cogl API. Currently only the nested X11 backend supports this mode fully, and the per view framebuffers are all offscreen. Upon frame completion, it'll blit each view's framebuffer onto the onscreen framebuffer before swapping. Other backends (X11 CM and native/KMS) are adapted to manage a full-stage view. The X11 CM backend will continue to use this method, while the native/KMS backend will be adopted to use multiple view drawing. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-26 23:09:24 -04:00
backends/meta-renderer-view.c \
backends/meta-renderer-view.h \
Move edid-parse to backends/
2014-04-01 14:34:52 -04:00
backends/edid-parse.c \
backends/edid.h \
backends: Build MetaBackend subclasses for each backend
2014-04-21 19:13:04 -04:00
backends/x11/meta-backend-x11.c \
backends/x11/meta-backend-x11.h \
barriers: Separate implementation from public API This patch removes the X11 specific code from MetaBarrier and creates an abstraction layer MetaBarrierImpl. The existing X11 implementation is moved to a new GObject MetaBarrierImplX11 implementing the abstract interface MetaBarrierImpl which is instantiated by MetaBarrier when supported. While at it, move it to backends/ and properly name the files. https://bugzilla.gnome.org/show_bug.cgi?id=706655
2015-01-15 21:30:04 -05:00
backends/x11/meta-barrier-x11.c \
backends/x11/meta-barrier-x11.h \
Make mutter manage its own clutter backends Introduce two new clutter backends: MetaClutterBackendX11 and MetaClutterBackendNative. They are so far only wrap ClutterBackendX11 and ClutterBackendEglNative respectively, but the aim is to move things from the original clutter backends when needed. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-04 04:19:23 -04:00
backends/x11/meta-clutter-backend-x11.c \
backends/x11/meta-clutter-backend-x11.h \
backends/x11: Move CRTC code to its own file Move code dealing with Xrandr MetaCrtcs and related functionality to its own file. Eventually, MetaCrtcCrtc should be introduced, based on MetaCrtc, and this commit is in preparation for that. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-07-04 13:11:19 -04:00
backends/x11/meta-crtc-xrandr.c \
backends/x11/meta-crtc-xrandr.h \
x11: Add simple cursor renderer
2014-04-27 10:49:29 -04:00
backends/x11/meta-cursor-renderer-x11.c \
backends/x11/meta-cursor-renderer-x11.h \
backends: Split out CRTC/output management to MetaGpu In order to eventually support multilpe GPUs with their own connectors, split out related meta data management (i.e. outputs, CRTCs and CRTC modes) into a new MetaGpu GObject. The Xrandr backend always assumes there is always only a single "GPU" as the GPU is abstracted by the X server; only the native backend (aside from the test backend) will eventually see more than one GPU. The Xrandr backend still moves some management to MetaGpuXrandr, in order to behave more similarly to the KMS counterparts. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-07-10 06:19:32 -04:00
backends/x11/meta-gpu-xrandr.c \
backends/x11/meta-gpu-xrandr.h \
backends/x11: Split up X11 backend into Cm and Nested Split up the X11 backend into two parts, one for running as a Compositing Manager, and one for running as a nested Wayland compositor. This commit also cleans up the compositor configuration calculation, attempting to make it more approachable. https://bugzilla.gnome.org/show_bug.cgi?id=777800
2017-01-27 10:04:02 -05:00
backends/x11/cm/meta-backend-x11-cm.c \
backends/x11/cm/meta-backend-x11-cm.h \
renderer-x11: Split up into CM and Nested renderers Split up the MetaRendererX11 class into one for when running as a X11 compositing manager, and one for when running as a nested Wayland compositor. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-17 03:00:54 -04:00
backends/x11/cm/meta-renderer-x11-cm.c \
backends/x11/cm/meta-renderer-x11-cm.h \
backends/x11: Split up X11 backend into Cm and Nested Split up the X11 backend into two parts, one for running as a Compositing Manager, and one for running as a nested Wayland compositor. This commit also cleans up the compositor configuration calculation, attempting to make it more approachable. https://bugzilla.gnome.org/show_bug.cgi?id=777800
2017-01-27 10:04:02 -05:00
backends/x11/nested/meta-backend-x11-nested.c \
backends/x11/nested/meta-backend-x11-nested.h \
backends/x11: Draw our own cursor sprite when running nested Use a specialized cursor renderer when running as a nested Wayand compositor. This new renderer sets an empty X11 cursor and draws the cursor as part of the stage using the generic cursor renderer drawing path. https://bugzilla.gnome.org/show_bug.cgi?id=744932
2015-07-16 22:40:51 -04:00
backends/x11/nested/meta-cursor-renderer-x11-nested.c \
backends/x11/nested/meta-cursor-renderer-x11-nested.h \
renderer-x11: Split up into CM and Nested renderers Split up the MetaRendererX11 class into one for when running as a X11 compositing manager, and one for when running as a nested Wayland compositor. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-03-17 03:00:54 -04:00
backends/x11/nested/meta-renderer-x11-nested.c \
backends/x11/nested/meta-renderer-x11-nested.h \
Start creating different subdirectories for each backend
2014-03-31 23:25:37 -04:00
backends/x11/meta-idle-monitor-xsync.c \
backends/x11/meta-idle-monitor-xsync.h \
backends/x11: Implement X11-specific MetaInputSettings This goes through modifying XI2 device properties, either common ones (eg. set on every device) or those specific to the libinput X11 driver. Keyboard repeat/rate are set through core and XKB APIs. https://bugzilla.gnome.org/show_bug.cgi?id=739397
2014-10-29 10:37:29 -04:00
backends/x11/meta-input-settings-x11.c \
backends/x11/meta-input-settings-x11.h \
Start creating different subdirectories for each backend
2014-03-31 23:25:37 -04:00
backends/x11/meta-monitor-manager-xrandr.c \
backends/x11/meta-monitor-manager-xrandr.h \
backends/x11: Move output code to its own file Move code dealing with X11 MetaOutputs and related functionality to its own file. Eventually, a MetaOutputXrandr should be introduced, based on MetaOutput, and this commit is in preparation for that. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-07-04 06:42:16 -04:00
backends/x11/meta-output-xrandr.c \
backends/x11/meta-output-xrandr.h \
Introduce MetaRenderer MetaRenderer is meant to be the object responsible for rendering the scene graph. It will contain the logic related to the cogl winsys backend, the clutter backend, and the clutter stage window. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-07 11:07:46 -04:00
backends/x11/meta-renderer-x11.c \
backends/x11/meta-renderer-x11.h \
Explicitly create per backend stage windows Split the stage window implementations into three separate objects: one for X11 as a compositing manager, one for X11 running as a nested Wayland compositor, and one for running with the native backend. The new stage window implementations are only thin shells; this is in preparation for making the stage windows behave more differently. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-20 03:58:10 -04:00
backends/x11/meta-stage-x11-nested.c \
backends/x11/meta-stage-x11-nested.h \
Move meta_ui_parse_accelerator into core/ We're currently using GTK+ for this, but we'll stop doing that fairly quickly and instead just copy the GTK+ code in-tree.
2014-04-07 10:48:16 -04:00
core/meta-accel-parse.c \
core/meta-accel-parse.h \
barrier: Add a new Meta wrapper for pointer barriers Currently, we have a few function wrappers in the shell for pointer barriers. If we want to implement interactive features on barriers, we need some sort of signal to be notified of the interactivity. In that case, we need to make a more sophisticated object-based wrapper for a pointer barrier. Add one, and stick it in mutter. https://bugzilla.gnome.org/show_bug.cgi?id=677215
2012-07-30 14:54:03 -04:00
meta/barrier.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/bell.c \
core/bell.h \
core/boxes.c \
introspection: remove --allow-unprefixed Remove --allow-unprefixed option to the scanner, and fix resulting problems: * theme.h and boxes.h are split into a main -header and a private header that includes stuff that is not generally useful and hard to introspect. Merge theme-parser.h into theme.h. * meta_display_get_atom() and meta_window_get_window_type_atom() are marked as (skip) * Fix annotation: (element-type Strut) => (element-type Meta.Strut) https://bugzilla.gnome.org/show_bug.cgi?id=632494
2010-10-18 14:34:14 -04:00
core/boxes-private.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/boxes.h \
Move out generic math parts out of the native barrier implementation In order to reuse some vector math for pointer confinement, move out those parts to its own file, introducing the types old types "MetaVector2" and "MetaLine2" outside of meta-barrier-native.c, as well as introducing MetaBorder which is a line, with a blocking direction. https://bugzilla.gnome.org/show_bug.cgi?id=744104
2015-07-03 03:01:58 -04:00
core/meta-border.c \
core/meta-border.h \
Add MetaFraction for dealing with fractions Add MetaFraction, which consists of two integers, the numerator an the denominator. The utility function to convert a double to a MetaFraction comes from gstreamer. https://bugzilla.gnome.org/show_bug.cgi?id=784199
2017-05-25 05:19:01 -04:00
core/meta-fraction.c \
core/meta-fraction.h \
compositor: export actor_is_untransformed function actor_is_untransformed is a function meta-window-group uses to determine if an actor is relatively pixel aligned and not contorted. It then returns the coordinates of the actor. In a subsequent commit will need the function in a different file, so this commit separates it out. https://bugzilla.gnome.org/show_bug.cgi?id=682427
2013-02-18 17:55:26 -05:00
compositor/clutter-utils.c \
compositor/clutter-utils.h \
Refactor "texture material" creation from MetaShadowFactory Create new cogl-utils.[ch] and move a helper function from MetaShadowFactory there as meta_create_texture_material(); this allows us to create single-layer materials from different parts of Mutter and have them share the same template material. Also expose a function for creating a 1x1 texture of a given color meta_create_color_texture_4ub(). https://bugzilla.gnome.org/show_bug.cgi?id=634833
2010-11-14 12:22:05 -05:00
compositor/cogl-utils.c \
compositor/cogl-utils.h \
Make MetaCompositor the clutter compositor * Move compositor-mutter.c to compositor.c * Remove the 'Mutter' typedef and define the structure for MetaCompositor directly. http://bugzilla.gnome.org/show_bug.cgi?id=581813
2009-06-25 16:29:20 -04:00
compositor/compositor.c \
Split shadow code into a separate file Separate code related to creating the gaussian-blurred shadow texture into a separate file. Move the definition of MetaCompositor into a compositor-private.h so that the shadow code can cache the source in the compositor structure. http://bugzilla.gnome.org/show_bug.cgi?id=587251
2009-06-25 18:56:15 -04:00
compositor/compositor-private.h \
compositor: rework how backgrounds are managed Background handling in GNOME is very roundabout at the moment. gnome-settings-daemon uses gnome-desktop to read the background from disk into a screen-sized pixmap. It then sets the XID of that pixmap on the _XROOTPMAP_ID root window property. mutter puts that pixmap into a texture/actor which gnome-shell then uses. Having the gnome-settings-daemon detour from disk to screen means we can't easily let the compositor handle transition effects when switching backgrounds. Also, having the background actor be per-screen instead of per-monitor means we may have oversized textures in certain multihead setups. This commit changes mutter to read backgrounds from disk itself, and it changes backgrounds to be per-monitor. This way background handling/compositing is left to the compositor. https://bugzilla.gnome.org/show_bug.cgi?id=682427
2013-01-23 15:54:41 -05:00
compositor/meta-background.c \
Rewrite background code The old requirement that multiple MetaBackgroundActor objects be layered on top of each to produce blended backgrounds resulted in extremely inefficient drawing since the entire framebuffer had to be read and written multiple times. * Replace the MetaBackground ClutterContent with a plain GObject that serves to hold the background parameters and prerender textures to be used to draw the background. It handles colors, gradients, and blended images, but does not handle vignetting * Add vignetting to MetaBackgroundActor directly. * Add MetaBackgroundImage and MetaBackgroundImageCache to allow multiple MetaBackground objects to share the same images By removing the usage of ClutterContent, the following optimizations were easy to add: Blending is turned off when the actor is fully opaque Nearest-neighbour filtering is used when drawing 1:1 The GLSL vignette code is slightly improved to use a vertex shader snippet for computing the texture coordinate => position in actor mapping. https://bugzilla.gnome.org/show_bug.cgi?id=735637
2014-08-10 11:26:14 -04:00
compositor/meta-background-private.h \
Draw the root window background Add code to track and draw the root window background. The advantage of doing it here as compared to in a plugin is that we can use the visiblity smarts of MetaWindowGroup to optimize out drawing the background when obscured. If handling other than tracking the _XROOTPMAP_ID property is desired in the future, more functionality like setting the background from a file or doing cross-fades can be added. The new background actor is exposed to plugins via meta_plugin_get_background_actor() similar to other exposed actors to allow cloning the background for use in other displays. The actual class is not installed for public consumption at the moment since it has no useful methods. https://bugzilla.gnome.org/show_bug.cgi?id=634833
2010-11-14 12:37:17 -05:00
compositor/meta-background-actor.c \
MetaBackgroundActor: make it a public class https://bugzilla.gnome.org/show_bug.cgi?id=656433
2011-08-28 21:20:29 -04:00
compositor/meta-background-actor-private.h \
Rewrite background code The old requirement that multiple MetaBackgroundActor objects be layered on top of each to produce blended backgrounds resulted in extremely inefficient drawing since the entire framebuffer had to be read and written multiple times. * Replace the MetaBackground ClutterContent with a plain GObject that serves to hold the background parameters and prerender textures to be used to draw the background. It handles colors, gradients, and blended images, but does not handle vignetting * Add vignetting to MetaBackgroundActor directly. * Add MetaBackgroundImage and MetaBackgroundImageCache to allow multiple MetaBackground objects to share the same images By removing the usage of ClutterContent, the following optimizations were easy to add: Blending is turned off when the actor is fully opaque Nearest-neighbour filtering is used when drawing 1:1 The GLSL vignette code is slightly improved to use a vertex shader snippet for computing the texture coordinate => position in actor mapping. https://bugzilla.gnome.org/show_bug.cgi?id=735637
2014-08-10 11:26:14 -04:00
compositor/meta-background-image.c \
compositor: rework how backgrounds are managed Background handling in GNOME is very roundabout at the moment. gnome-settings-daemon uses gnome-desktop to read the background from disk into a screen-sized pixmap. It then sets the XID of that pixmap on the _XROOTPMAP_ID root window property. mutter puts that pixmap into a texture/actor which gnome-shell then uses. Having the gnome-settings-daemon detour from disk to screen means we can't easily let the compositor handle transition effects when switching backgrounds. Also, having the background actor be per-screen instead of per-monitor means we may have oversized textures in certain multihead setups. This commit changes mutter to read backgrounds from disk itself, and it changes backgrounds to be per-monitor. This way background handling/compositing is left to the compositor. https://bugzilla.gnome.org/show_bug.cgi?id=682427
2013-01-23 15:54:41 -05:00
compositor/meta-background-group.c \
cullable: Turn cull_out / reset_culling into a separate interface Instead of hardcoded knowledge of certain classes in MetaWindowGroup, create a generic interface that all actors can implement to get parts of their regions culled out during redraw, without needing any special knowledge of how to handle a specific actor. The names now are a bit suspect. MetaBackgroundGroup is a simple MetaCullable that knows how to cull children, and MetaWindowGroup is the "toplevel" cullable that computes the initial two regions. A future cleanup here could be to merge MetaWindowGroup / MetaBackgroundGroup so that we only have a generic MetaSimpleCullable, and move the "toplevel" cullability to be a MetaCullableToplevel. https://bugzilla.gnome.org/show_bug.cgi?id=714706
2013-11-21 15:25:08 -05:00
compositor/meta-cullable.c \
compositor/meta-cullable.h \
dnd: Implement MetaDnd Implement MetaDnd for emitting DnD signals to plugins such as gnome-shell. The xdnd handling code comes from gnome-shell, and it is hidden behind MetaDnd now. https://bugzilla.gnome.org/show_bug.cgi?id=765003
2017-01-02 09:11:32 -05:00
compositor/meta-dnd.c \
compositor: Add MetaDnDActor This actor is a subclass of MetaFeedbackActor that additionally implements the "drag failed" animation, snapping back to the drag origin position in a surface.
2014-10-06 10:53:04 -04:00
compositor/meta-dnd-actor.c \
compositor/meta-dnd-actor-private.h \
compositor: Add MetaFeedbackActor This actor is a non-reactive container that autoembeds itself into the feedback window group in the compositor. The API is meant to help on creating things attached to pointer/touchpoints, with an X/Y attachment offset, and following the position of certain events.
2014-10-06 10:50:15 -04:00
compositor/meta-feedback-actor.c \
compositor/meta-feedback-actor-private.h \
Remove Mutter namespace prefix Move all objects and functions namespaced with Mutter into the Meta namespace to get a single consistent namespace. Changes that aren't simply changing mutter to meta: MutterWindow => MetaWindowActor mutter_get_windows => meta_get_window_actors mutter_plugin_get_windows => meta_plugin_get_window_actors https://bugzilla.gnome.org/show_bug.cgi?id=628520
2010-10-18 13:27:14 -04:00
compositor/meta-module.c \
compositor/meta-module.h \
compositor/meta-plugin.c \
compositor/meta-plugin-manager.c \
compositor/meta-plugin-manager.h \
Make shadows pretty and configurable The current shadow code just uses a single fixed texture (the Gaussian blur of a rectangle with a fixed blur radius) for drawing all window shadows. This patch adds the ability * Implement efficient blurring of arbitrary regions by approximating a Gaussian blur with multiple box blurs. * Detect when multiple windows can use the same shadow texture by converting their shape into a size-invariant MetaWindowShape. * Add properties shadow-radius, shadow-x-offset, shadow-y-offset, shadow-opacity to allow the shadow for a window to be configured. * Add meta_window_actor_paint() and draw the shadow directly from there rather than using a child actor. * Remove TidyTextureFrame, which is no longer used https://bugzilla.gnome.org/show_bug.cgi?id=592382
2010-10-18 15:34:08 -04:00
compositor/meta-shadow-factory.c \
Remove Mutter namespace prefix Move all objects and functions namespaced with Mutter into the Meta namespace to get a single consistent namespace. Changes that aren't simply changing mutter to meta: MutterWindow => MetaWindowActor mutter_get_windows => meta_get_window_actors mutter_plugin_get_windows => meta_plugin_get_window_actors https://bugzilla.gnome.org/show_bug.cgi?id=628520
2010-10-18 13:27:14 -04:00
compositor/meta-shaped-texture.c \
MetaShapedTexture: don't include private headers in public ones Private headers are not installed, so they can't be referenced from public ones. https://bugzilla.gnome.org/show_bug.cgi?id=705497
2013-08-16 08:23:40 -04:00
compositor/meta-shaped-texture-private.h \
Introduce MetaSurfaceActor for drawing MetaWindowActor content Instead of having MetaWindowActor only have one single MetaShapedTexture as actor drawing its content, introduce a new abstract MetaSurfaceActor that takes care of drawing. This is one step in the direction to decouple MetaWaylandSurface with a MetaWindow and MetaWindowActor (except for shell/xdg surfaces) in order to finally support subsurfaces like features, or any feature where window is not drawn using a single texture. The first step, implemented in this patch, is to not have MetaWindowActor work directly with a shaped texture. There are still some cases where it simply gets the texture and goes on as before, but this should be changed by either removing the need of going via MetaWindowActor or by adding some generic interface to MetaSurfaceActor that doesn't limit its functionality to one shaped texture. There should be no visible difference nor after this patch, but meta_window_actor_get_texture() and meta_surface_actor_get_texture() should be deprecated when equivalent functionality has been introduced. Signed-off-by: Jonas Ådahl <jadahl@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=705502
2013-10-13 07:47:53 -04:00
compositor/meta-surface-actor.c \
compositor/meta-surface-actor.h \
window-actor: Split into two subclasses of MetaSurfaceActor The rendering logic before was somewhat complex. We had three independent cases to take into account when doing rendering: * X11 compositor. In this case, we're a traditional X11 compositor, not a Wayland compositor. We use XCompositeNameWindowPixmap to get the backing pixmap for the window, and deal with the COMPOSITE extension messiness. In this case, meta_is_wayland_compositor() is FALSE. * Wayland clients. In this case, we're a Wayland compositor managing Wayland surfaces. The rendering for this is fairly straightforward, as Cogl handles most of the complexity with EGL and SHM buffers... Wayland clients give us the input and opaque regions through wl_surface. In this case, meta_is_wayland_compositor() is TRUE and priv->window->client_type == META_WINDOW_CLIENT_TYPE_WAYLAND. * XWayland clients. In this case, we're a Wayland compositor, like above, and XWayland hands us Wayland surfaces. XWayland handles the COMPOSITE extension messiness for us, and hands us a buffer like any other Wayland client. We have to fetch the input and opaque regions from the X11 window ourselves. In this case, meta_is_wayland_compositor() is TRUE and priv->window->client_type == META_WINDOW_CLIENT_TYPE_X11. We now split the rendering logic into two subclasses, which are: * MetaSurfaceActorX11, which handles the X11 compositor case, in that it uses XCompositeNameWindowPixmap to get the backing pixmap, and deal with all the COMPOSITE extension messiness. * MetaSurfaceActorWayland, which handles the Wayland compositor case for both native Wayland clients and XWayland clients. XWayland handles COMPOSITE for us, and handles pushing a surface over through the xf86-video-wayland DDX. Frame sync is still in MetaWindowActor, as it needs to work for both the X11 compositor and XWayland client cases. When Wayland's video display protocol lands, this will need to be significantly overhauled, as it would have to work for any wl_surface, including subsurfaces, so we would need surface-level discretion. https://bugzilla.gnome.org/show_bug.cgi?id=720631
2014-02-01 17:21:11 -05:00
compositor/meta-surface-actor-x11.c \
compositor/meta-surface-actor-x11.h \
compositor: Add support for GL_EXT_x11_sync_object If GL advertises this extension we'll use it to synchronize X with GL rendering instead of relying on the XSync() behavior with open source drivers. Some driver bugs were uncovered while working on this so if we have had to reboot the ring a few times, something is probably wrong and we're likely to just make things worse by continuing to try. Let's err on the side of caution, disable ourselves and fallback to the XSync() path in the compositor. https://bugzilla.gnome.org/show_bug.cgi?id=728464
2014-04-18 14:21:20 -04:00
compositor/meta-sync-ring.c \
compositor/meta-sync-ring.h \
Use a utility function to create GL_ARB_texture_rectangles meta-texture-rectangle and meta-shaped-texture both create textures with GL_TEXTURE_RECTANGLE_ARB as the target using direct GL calls. This patch moves that code into a shared utility function in a separate file instead. The function resolves the required GL symbols dynamically instead of linking to them directly so that if Clutter eventually stops linking to -lGL mutter will continue to build. The function also splits the texture creation into a separate texture creation and data upload stage so that it can use cogl_texture_set_region to upload the data. That way it can avoid clobbering the glPixelStore state and it can let Cogl do any necessary format conversion. The code preserves the old value of the rectangle texture binding instead of clobbering it because Cogl expects to be able to cache this value to avoid redundant glBindTexture calls. Finally, the function uses cogl_object_set_data to automatically destroy the GL texture when the Cogl texture is destroyed. This avoids having to have special code to destroy the cogl texture. https://bugzilla.gnome.org/show_bug.cgi?id=654569
2011-07-13 10:47:10 -04:00
compositor/meta-texture-rectangle.c \
compositor/meta-texture-rectangle.h \
Remove Mutter namespace prefix Move all objects and functions namespaced with Mutter into the Meta namespace to get a single consistent namespace. Changes that aren't simply changing mutter to meta: MutterWindow => MetaWindowActor mutter_get_windows => meta_get_window_actors mutter_plugin_get_windows => meta_plugin_get_window_actors https://bugzilla.gnome.org/show_bug.cgi?id=628520
2010-10-18 13:27:14 -04:00
compositor/meta-texture-tower.c \
compositor/meta-texture-tower.h \
compositor/meta-window-actor.c \
compositor/meta-window-actor-private.h \
compositor/meta-window-group.c \
compositor/meta-window-group.h \
Make shadows pretty and configurable The current shadow code just uses a single fixed texture (the Gaussian blur of a rectangle with a fixed blur radius) for drawing all window shadows. This patch adds the ability * Implement efficient blurring of arbitrary regions by approximating a Gaussian blur with multiple box blurs. * Detect when multiple windows can use the same shadow texture by converting their shape into a size-invariant MetaWindowShape. * Add properties shadow-radius, shadow-x-offset, shadow-y-offset, shadow-opacity to allow the shadow for a window to be configured. * Add meta_window_actor_paint() and draw the shadow directly from there rather than using a child actor. * Remove TidyTextureFrame, which is no longer used https://bugzilla.gnome.org/show_bug.cgi?id=592382
2010-10-18 15:34:08 -04:00
compositor/meta-window-shape.c \
compositor/region-utils.c \
compositor/region-utils.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/compositor.h \
compositor: rework how backgrounds are managed Background handling in GNOME is very roundabout at the moment. gnome-settings-daemon uses gnome-desktop to read the background from disk into a screen-sized pixmap. It then sets the XID of that pixmap on the _XROOTPMAP_ID root window property. mutter puts that pixmap into a texture/actor which gnome-shell then uses. Having the gnome-settings-daemon detour from disk to screen means we can't easily let the compositor handle transition effects when switching backgrounds. Also, having the background actor be per-screen instead of per-monitor means we may have oversized textures in certain multihead setups. This commit changes mutter to read backgrounds from disk itself, and it changes backgrounds to be per-monitor. This way background handling/compositing is left to the compositor. https://bugzilla.gnome.org/show_bug.cgi?id=682427
2013-01-23 15:54:41 -05:00
meta/meta-background.h \
MetaBackgroundActor: make it a public class https://bugzilla.gnome.org/show_bug.cgi?id=656433
2011-08-28 21:20:29 -04:00
meta/meta-background-actor.h \
Rewrite background code The old requirement that multiple MetaBackgroundActor objects be layered on top of each to produce blended backgrounds resulted in extremely inefficient drawing since the entire framebuffer had to be read and written multiple times. * Replace the MetaBackground ClutterContent with a plain GObject that serves to hold the background parameters and prerender textures to be used to draw the background. It handles colors, gradients, and blended images, but does not handle vignetting * Add vignetting to MetaBackgroundActor directly. * Add MetaBackgroundImage and MetaBackgroundImageCache to allow multiple MetaBackground objects to share the same images By removing the usage of ClutterContent, the following optimizations were easy to add: Blending is turned off when the actor is fully opaque Nearest-neighbour filtering is used when drawing 1:1 The GLSL vignette code is slightly improved to use a vertex shader snippet for computing the texture coordinate => position in actor mapping. https://bugzilla.gnome.org/show_bug.cgi?id=735637
2014-08-10 11:26:14 -04:00
meta/meta-background-image.h \
compositor: rework how backgrounds are managed Background handling in GNOME is very roundabout at the moment. gnome-settings-daemon uses gnome-desktop to read the background from disk into a screen-sized pixmap. It then sets the XID of that pixmap on the _XROOTPMAP_ID root window property. mutter puts that pixmap into a texture/actor which gnome-shell then uses. Having the gnome-settings-daemon detour from disk to screen means we can't easily let the compositor handle transition effects when switching backgrounds. Also, having the background actor be per-screen instead of per-monitor means we may have oversized textures in certain multihead setups. This commit changes mutter to read backgrounds from disk itself, and it changes backgrounds to be per-monitor. This way background handling/compositing is left to the compositor. https://bugzilla.gnome.org/show_bug.cgi?id=682427
2013-01-23 15:54:41 -05:00
meta/meta-background-group.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/meta-plugin.h \
meta/meta-shadow-factory.h \
meta/meta-window-actor.h \
Export the shadow factory The elementary guys would like this as an API, and I don't see any reason to refuse -- this is quite nice shadow painting code :) For some reason, gobject-introspection can't seem to cope with MetaWindowShape. I'll look into it a bit later, but for now, mark the function it has trouble with as (skip).
2015-07-06 03:02:13 -04:00
meta/meta-window-shape.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/compositor-mutter.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/constraints.c \
core/constraints.h \
core/core.c \
core: Add MetaCloseDialog This is an interface that can be used to implement the "application is not responding" dialog. One instance is created per window, which is initially hidden, and can be shown/hidden on demand. https://bugzilla.gnome.org/show_bug.cgi?id=711619
2016-07-11 07:07:46 -04:00
core/meta-close-dialog.c \
meta/meta-close-dialog.h \
core: Implement MetaCloseDialogDefault This is basically a copy of the implementation currently residing in src/core/delete.c, which will be eventually deleted in favor of this one. https://bugzilla.gnome.org/show_bug.cgi?id=711619
2016-07-11 07:12:13 -04:00
core/meta-close-dialog-default.c \
core/meta-close-dialog-default-private.h \
core: add MetaInhibitShortcutsDialog Add a new interface for allowing or denying shortcuts inhibit requests. https://bugzilla.gnome.org/show_bug.cgi?id=783342
2017-06-14 04:54:16 -04:00
core/meta-inhibit-shortcuts-dialog.c \
meta/meta-inhibit-shortcuts-dialog.h \
wayland: use the inhibit shortcuts dialog Plug the new MetaInhbitShortcutsDialog to the relevant Wayland protocol implementation. Also, remember the last user choice for a given surface to avoid asking continuously the same question. https://bugzilla.gnome.org/show_bug.cgi?id=783342
2017-06-14 05:27:14 -04:00
core/meta-inhibit-shortcuts-dialog-default.c \
core/meta-inhibit-shortcuts-dialog-default-private.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/delete.c \
core/display.c \
src/include/frame.h src/include/display.h src/include/xprops.h 2008-05-19 Iain Holmes <iain@gnome.org> * src/include/frame.h * src/include/display.h * src/include/xprops.h * src/include/compositor.h * src/include/types.h * src/include/window.h * src/include/errors.h * src/include/screen.h: New basic public API for compositor. * src/compositor/*: Separate the compositor out into its own separate directory and set it up for backends. Initial XRender backend. * src/core/compositor.[ch]: Remove * src/core/frame.h * src/core/screen.h * src/core/display.h * src/core/window.h: Rename to -private.h so as not to clash with the new files in include * src/core/delete.c * src/core/workspace.h * src/core/stack.[ch] * src/core/keybindings.[ch] * src/core/errors.c * src/core/effects.[ch] * src/core/core.c * src/core/group.h * src/core/edge-resistance.[ch] * src/core/window-props.[ch] * src/core/constraints.h * src/core/bell.[ch] * src/core/iconcache.h * src/core/session.[ch] * src/core/main.c * src/core/place.h * src/core/xprops.c * src/ui/tabpopup.c: Use the new -private headers * src/core/display.c * src/core/frame.c * src/core/window.c * src/core/screen.c: Add the API functions required by the compositor * src/Makefile.am: Relocate the new files svn path=/trunk/; revision=3715
2008-05-18 20:00:09 -04:00
core/display-private.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/display.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/edge-resistance.c \
core/edge-resistance.h \
Move event handling to a new file display.c is getting a bit crowded. Move most of the handling out to another file, events.c. The long-term goal is to have generic event handling here, with backend-specific handling for the types of windows and such.
2014-03-20 15:29:30 -04:00
core/events.c \
core/events.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/errors.c \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/errors.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/frame.c \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
core/frame.h \
gesture-tracker: Rename files to include the meta- prefix
2014-07-08 13:29:22 -04:00
core/meta-gesture-tracker.c \
core/meta-gesture-tracker-private.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/keybindings.c \
Install keybindings.h
2009-01-29 10:14:25 -05:00
core/keybindings-private.h \
build: Update src/Makefile.am https://bugzilla.gnome.org/show_bug.cgi?id=778699
2017-02-15 12:17:34 -05:00
core/main-private.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/main.c \
core/place.c \
core/place.h \
core/prefs.c \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/prefs.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/screen.c \
src/include/frame.h src/include/display.h src/include/xprops.h 2008-05-19 Iain Holmes <iain@gnome.org> * src/include/frame.h * src/include/display.h * src/include/xprops.h * src/include/compositor.h * src/include/types.h * src/include/window.h * src/include/errors.h * src/include/screen.h: New basic public API for compositor. * src/compositor/*: Separate the compositor out into its own separate directory and set it up for backends. Initial XRender backend. * src/core/compositor.[ch]: Remove * src/core/frame.h * src/core/screen.h * src/core/display.h * src/core/window.h: Rename to -private.h so as not to clash with the new files in include * src/core/delete.c * src/core/workspace.h * src/core/stack.[ch] * src/core/keybindings.[ch] * src/core/errors.c * src/core/effects.[ch] * src/core/core.c * src/core/group.h * src/core/edge-resistance.[ch] * src/core/window-props.[ch] * src/core/constraints.h * src/core/bell.[ch] * src/core/iconcache.h * src/core/session.[ch] * src/core/main.c * src/core/place.h * src/core/xprops.c * src/ui/tabpopup.c: Use the new -private headers * src/core/display.c * src/core/frame.c * src/core/window.c * src/core/screen.c: Add the API functions required by the compositor * src/Makefile.am: Relocate the new files svn path=/trunk/; revision=3715
2008-05-18 20:00:09 -04:00
core/screen-private.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/screen.h \
core: Refactor startup notification into a separate object This is kind of in a middle ground at the moment. Even though it handles sequences not coming from libsn, they're added nowhere at the moment, we'll rely on the app launch context being in the x11 side at the moment. Also, even though we do create internal sequence objects, we keep exposing SnStartupSequences to make gnome-shell happy, we could consider making this object "public" (and the sequence objects with it), things stay private at the moment. https://bugzilla.gnome.org/show_bug.cgi?id=762268
2016-02-06 08:52:03 -05:00
core/startup-notification.c \
core/startup-notification-private.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/types.h \
Add a framework for restarting the compositor with nice visuals The current GNOME Shell Alt-F2 restart looks very messy and also provides no indication to the user what is going on. We need to restart the compositor to switch in and out of stereo mode, so add a framework for doing this more cleanly: Additions: meta_restart(): restarts the compositor with a message MetaDisplay::show-restart-message: signal the embedding shell to show a message MetaDisplay::restart: signal the embedding shell to restart itself. meta_is_restart(): indicates whether the current instance is a restart so we can suppress login animations. A helper program meta-restart-helper holds the composite overlay window up during the restart to avoid visual artifacts. https://bugzilla.gnome.org/show_bug.cgi?id=733026
2014-05-08 18:35:49 -04:00
core/restart.c \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/stack.c \
core/stack.h \
Add better tracking of real stacking order Wedging override-redirect windows into the constraint code in stack.c results in Mutter getting confused about the stacking order of these windows with respect to other windows, and may also in some cases cause Mutter to restack override-redirect windows. core/stack-tracker.c core/stack-tracker.h: MetaStackTracker - combine events received from the X server with local changes we have made to come up with the best possible idea of what the stacking order is at any one point in time. core/screen.c core/screen-private.h: Create a MetaStackTracker for the screen. core/display.c: Feed relevant events to MetaStackTracker core/frame.c core/screen.c core/stack.c: When we make changes to the stacking order or add windows, record those changes immediatley in MetaStackTracker so we have the information without waiting for a round-trip. include/ui.h ui/ui.c: meta_ui_create_frame_window add a return value for the X request serial used to create the window. http://bugzilla.gnome.org/show_bug.cgi?id=585984
2009-06-13 16:45:32 -04:00
core/stack-tracker.c \
core/stack-tracker.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/util.c \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/util.h \
Fix regression in mutter-wayland translations Switching meta/util.h to gi18n.h was wrong, mutter is a library and needs gi18n-lib.h, but that cannot be included from a public header (since it depends on config.h or command line options), so split util.h into a public and a private part. https://bugzilla.gnome.org/show_bug.cgi?id=707897
2013-09-11 04:18:53 -04:00
core/util-private.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/window.c \
src/include/frame.h src/include/display.h src/include/xprops.h 2008-05-19 Iain Holmes <iain@gnome.org> * src/include/frame.h * src/include/display.h * src/include/xprops.h * src/include/compositor.h * src/include/types.h * src/include/window.h * src/include/errors.h * src/include/screen.h: New basic public API for compositor. * src/compositor/*: Separate the compositor out into its own separate directory and set it up for backends. Initial XRender backend. * src/core/compositor.[ch]: Remove * src/core/frame.h * src/core/screen.h * src/core/display.h * src/core/window.h: Rename to -private.h so as not to clash with the new files in include * src/core/delete.c * src/core/workspace.h * src/core/stack.[ch] * src/core/keybindings.[ch] * src/core/errors.c * src/core/effects.[ch] * src/core/core.c * src/core/group.h * src/core/edge-resistance.[ch] * src/core/window-props.[ch] * src/core/constraints.h * src/core/bell.[ch] * src/core/iconcache.h * src/core/session.[ch] * src/core/main.c * src/core/place.h * src/core/xprops.c * src/ui/tabpopup.c: Use the new -private headers * src/core/display.c * src/core/frame.c * src/core/window.c * src/core/screen.c: Add the API functions required by the compositor * src/Makefile.am: Relocate the new files svn path=/trunk/; revision=3715
2008-05-18 20:00:09 -04:00
core/window-private.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/window.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
core/workspace.c \
Distcheck fixes.
2009-02-12 05:48:59 -05:00
core/workspace-private.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/common.h \
core/core.h \
ui/ui.h \
sort source files into these directories according to which part of the WM 2007-12-19 Havoc Pennington <hp@redhat.com> * src/ui, src/core, src/include: sort source files into these directories according to which part of the WM they are supposed to be in. In an eventual plan, we should also create src/compositor/render, src/compositor/fallback and move some of the compositor stuff into that. * autogen.sh: require a newer automake, so we don't have to use a recursive build * src/ui/tabpopup.c: put in a hack to make the build temporarily work, want to commit the large rearrangement before fixing this not to include workspace.h or frame.h * src/core/iconcache.c (meta_read_icons): temporarily break this to get the build to work, want to commit the large rearrangement before fixing this file not to include theme.h svn path=/trunk/; revision=3491
2007-12-19 16:17:50 -05:00
ui/frames.c \
ui/frames.h \
ui/theme.c \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/theme.h \
introspection: remove --allow-unprefixed Remove --allow-unprefixed option to the scanner, and fix resulting problems: * theme.h and boxes.h are split into a main -header and a private header that includes stuff that is not generally useful and hard to introspect. Merge theme-parser.h into theme.h. * meta_display_get_atom() and meta_window_get_window_type_atom() are marked as (skip) * Fix annotation: (element-type Strut) => (element-type Meta.Strut) https://bugzilla.gnome.org/show_bug.cgi?id=632494
2010-10-18 14:34:14 -04:00
ui/theme-private.h \
Kill HAVE_WAYLAND
2014-02-17 21:28:41 -05:00
ui/ui.c \
Move atomnames.h to x11/ This should *not* be part of the public API.
2015-04-27 19:36:46 -04:00
x11/atomnames.h \
Move all X11 event processing to a new file in x11/
2014-06-11 16:08:33 -04:00
x11/events.c \
x11/events.h \
Revert "Move MetaGroup to be X11-specific" This reverts commit f940292cfe5a80290a5dae8a62e05fbcbab32a7f. Turns out MetaGroup was public API and was used by gnome-shell. Ugh.
2014-03-19 09:11:23 -04:00
x11/group-private.h \
Start moving X11 implementation to its own subdirectory This is specifically about managing X11 windows, not necessarily running as an X11 compositor. By that I mean that this code is still used for XWayland windows, and event handling is still and modesetting / monitor management is still in core/. This is also a fairly conservative move. We don't move anything like screen.c or bell.c in here, even though those are really only for X11 clients.
2014-03-18 12:57:08 -04:00
x11/group-props.c \
x11/group-props.h \
x11/group.c \
Revert "Move MetaGroup to be X11-specific" This reverts commit f940292cfe5a80290a5dae8a62e05fbcbab32a7f. Turns out MetaGroup was public API and was used by gnome-shell. Ugh.
2014-03-19 09:11:23 -04:00
meta/group.h \
Move atomnames.h to x11/ This should *not* be part of the public API.
2015-04-27 19:36:46 -04:00
x11/iconcache.c \
x11/iconcache.h \
Move session to x11/ XSMP code is X11-specific, of course.
2014-03-18 22:02:47 -04:00
x11/session.c \
x11/session.h \
Start moving X11 implementation to its own subdirectory This is specifically about managing X11 windows, not necessarily running as an X11 compositor. By that I mean that this code is still used for XWayland windows, and event handling is still and modesetting / monitor management is still in core/. This is also a fairly conservative move. We don't move anything like screen.c or bell.c in here, even though those are really only for X11 clients.
2014-03-18 12:57:08 -04:00
x11/window-props.c \
x11/window-props.h \
x11/window-x11.c \
x11/window-x11.h \
x11/window-x11-private.h \
x11/xprops.c \
x11/xprops.h \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
x11/mutter-Xatomtype.h \
$(NULL)
Conditionalize Wayland support again
2014-08-13 20:19:35 -04:00
Add remote desktop and screen cast functionality This commit adds basic screen casting and remote desktoping functionalty. This works by exposing two D-Bus API services: org.gnome.Mutter.ScreenCast and org.gnome.Mutter.RemoteDesktop. The remote desktop API is used to create remote desktop sessions. For each session, a D-Bus object is created, and an application can manage the session by sending messages to the session object. A remote desktop session the user to emit input events using the D-Bus methods on the session object. To get framebuffer content, the application should create an associated screen cast session. The screen cast API is used to create screen cast sessions. One can so far either create stand-alone screen cast sessions, or a screen cast session associated with a remote desktop session. A remote desktop associated screen cast session is managed by the remote desktop session. So far only remote desktop managed screen cast sessions are implemented. Each screen cast session may have one or more streams. A screen cast stream is a stream of buffers of some part of the compositor content. So far API exists for creating streams of monitors and windows, but only monitor streams are implemented. When a screen cast session is started, the one PipeWire stream is created for each screen cast stream created for the session. When this has happened, a PipeWireStreamAdded signal is emitted on the stream object, passing a unique identifier. The application may use this identifier to find the associated stream being advertised by the PipeWire daemon. The remote desktop and screen cast functionality must be explicitly be enabled at ./configure time by passing --enable-remote-desktop to ./configure. Doing this will build both screen cast and remote desktop support. To actually enable the screen casting and remote desktop, the user must enable the experimental feature. See org.gnome.mutter.experimental-features. https://bugzilla.gnome.org/show_bug.cgi?id=784199
2017-06-21 02:23:44 -04:00
if HAVE_REMOTE_DESKTOP
libmutter_@LIBMUTTER_API_VERSION@_la_SOURCES += \
backends/meta-dbus-session-watcher.c \
backends/meta-dbus-session-watcher.h \
backends/meta-remote-desktop.c \
backends/meta-remote-desktop.h \
backends/meta-remote-desktop-session.c \
backends/meta-remote-desktop-session.h \
backends/meta-screen-cast.c \
backends/meta-screen-cast.h \
backends/meta-screen-cast-monitor-stream.c \
backends/meta-screen-cast-monitor-stream.h \
backends/meta-screen-cast-monitor-stream-src.c \
backends/meta-screen-cast-monitor-stream-src.h \
backends/meta-screen-cast-session.c \
backends/meta-screen-cast-session.h \
backends/meta-screen-cast-stream.c \
backends/meta-screen-cast-stream.h \
backends/meta-screen-cast-stream-src.c \
backends/meta-screen-cast-stream-src.h \
$(NULL)
endif
Conditionalize Wayland support again
2014-08-13 20:19:35 -04:00
if HAVE_WAYLAND
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
libmutter_@LIBMUTTER_API_VERSION@_la_SOURCES += \
Conditionalize Wayland support again
2014-08-13 20:19:35 -04:00
compositor/meta-surface-actor-wayland.c \
compositor/meta-surface-actor-wayland.h \
wayland: Adds basic hybrid X + Wayland support This adds support for running mutter as a hybrid X and Wayland compositor. It runs a headless XWayland server for X applications that presents wayland surfaces back to mutter which mutter can then composite. This aims to not break Mutter's existing support for the traditional X compositing model which means a single build of Mutter can be distributed supporting the traditional model and the new Wayland based compositing model. TODO: although building with --disable-wayland has at least been tested, I still haven't actually verified that running as a traditional compositor isn't broken currently. Note: At this point no input is supported Note: multiple authors have contributed to this patch: Authored-by: Robert Bragg <robert@linux.intel.com> Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Rico Tzschichholz. Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2012-01-07 17:21:32 -05:00
wayland/meta-wayland.c \
wayland: Move "public" Wayland API to another header file
2014-02-28 10:24:06 -05:00
wayland/meta-wayland.h \
wayland: Adds basic hybrid X + Wayland support This adds support for running mutter as a hybrid X and Wayland compositor. It runs a headless XWayland server for X applications that presents wayland surfaces back to mutter which mutter can then composite. This aims to not break Mutter's existing support for the traditional X compositing model which means a single build of Mutter can be distributed supporting the traditional model and the new Wayland based compositing model. TODO: although building with --disable-wayland has at least been tested, I still haven't actually verified that running as a traditional compositor isn't broken currently. Note: At this point no input is supported Note: multiple authors have contributed to this patch: Authored-by: Robert Bragg <robert@linux.intel.com> Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Rico Tzschichholz. Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2012-01-07 17:21:32 -05:00
wayland/meta-wayland-private.h \
wayland: Add basic input support This copies the basic input support from the Clayland demo compositor. It adds a basic wl_seat implementation which can convert Clutter mouse events to Wayland events. For this to work all of the wayland surface actors need to be made reactive. The wayland keyboard input focus surface is updated whenever Mutter sees a FocusIn event so that it will stay in synch with whatever surface Mutter wants as the focus. Wayland surfaces don't get this event so for now it will just give them focus whenever they are clicked as a hack to test the code. Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2013-05-03 13:51:22 -04:00
wayland/meta-xwayland.c \
xwayland: Switch to the new Xwayland DDX
2014-03-20 13:12:43 -04:00
wayland/meta-xwayland.h \
wayland: Add X11/wayland selection interoperation This piece of code hooks in both wl_data_device and the relevant X selection events, an X11 Window is set up so it can act as the clipboard owner when any wayland client owns the selection, reacting to SelectionRequest events, and returning the data from the wayland client FD to any X11 requestor through X properties. In the opposite direction, SelectionNotify messages are received, which results in the property contents being converted then written into the wayland requestor's FD. This code also takes care of the handling incremental transfers through the INCR property type, reading/writing data chunk by chunk. https://bugzilla.gnome.org/show_bug.cgi?id=738312
2014-10-10 12:55:00 -04:00
wayland/meta-xwayland-selection.c \
wayland: Make MetaWaylandDataSource ownership protocol specific Firstly, this patch makes MetawaylandDataSource a GObject. This is in order to easier track its lifetime without adding destroy signals etc. It also makes the vfunc table GObject class functions instead while at it, as well as moves protocol specific part of the source into their own implementations. An important part of this patch is the change of ownership. Prior to this patch, MetaWaylandDataDevice would kind of own the source, but for Wayland sources it would remove it if the corresponding wl_resource was destroyed. For XWayland clients it would own it completely, and only remove it if the source was replaced. This patch changes so that the protocol implementation owns the source. For Wayland sources, the wl_resource owns the source, and the MetaWaylandDataDevice sets a weak reference (so in other words, no semantical changes really). For XWayland sources, the source is owned by the selection bridge, and not removed until replaced or if the client goes away. Given the changes in ownership, data offers may now properly track the lifetime of a source it represents. Prior to this patch, if an offer with an XWayland source would loose its source, it wouldn't get notified and have an invalid pointer it would potentally crash on. For Wayland sources, an offer would have a weak reference and clean itself up if the source went away. This patch changes so the behavior is consistent, meaning a weak reference is added to the source GObject so that the offer can behave correctly both for Wayland sources and XWayland sources. https://bugzilla.gnome.org/show_bug.cgi?id=750680
2015-06-17 22:25:11 -04:00
wayland/meta-xwayland-selection-private.h \
xwayland: Switch to the new Xwayland DDX
2014-03-20 13:12:43 -04:00
wayland/meta-xwayland-private.h \
wayland: Put the MetaWaylandBuffer implementation in a new file
2014-10-07 22:39:00 -04:00
wayland/meta-wayland-buffer.c \
wayland/meta-wayland-buffer.h \
wayland: Add zwp_linux_dmabuf_v1 support https://bugzilla.gnome.org/show_bug.cgi?id=785262 Signed-off-by: Daniel Stone <daniels@collabora.com>
2017-07-11 11:03:26 -04:00
wayland/meta-wayland-dma-buf.c \
wayland/meta-wayland-dma-buf.h \
wayland: Move MetaWaylandRegion into a new file as well
2014-10-07 23:12:36 -04:00
wayland/meta-wayland-region.c \
wayland/meta-wayland-region.h \
wayland: Add basic input support This copies the basic input support from the Clayland demo compositor. It adds a basic wl_seat implementation which can convert Clutter mouse events to Wayland events. For this to work all of the wayland surface actors need to be made reactive. The wayland keyboard input focus surface is updated whenever Mutter sees a FocusIn event so that it will stay in synch with whatever surface Mutter wants as the focus. Wayland surfaces don't get this event so for now it will just give them focus whenever they are clicked as a hack to test the code. Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2013-05-03 13:51:22 -04:00
wayland/meta-wayland-data-device.c \
wayland/meta-wayland-data-device.h \
wayland: Make MetaWaylandDataSource ownership protocol specific Firstly, this patch makes MetawaylandDataSource a GObject. This is in order to easier track its lifetime without adding destroy signals etc. It also makes the vfunc table GObject class functions instead while at it, as well as moves protocol specific part of the source into their own implementations. An important part of this patch is the change of ownership. Prior to this patch, MetaWaylandDataDevice would kind of own the source, but for Wayland sources it would remove it if the corresponding wl_resource was destroyed. For XWayland clients it would own it completely, and only remove it if the source was replaced. This patch changes so that the protocol implementation owns the source. For Wayland sources, the wl_resource owns the source, and the MetaWaylandDataDevice sets a weak reference (so in other words, no semantical changes really). For XWayland sources, the source is owned by the selection bridge, and not removed until replaced or if the client goes away. Given the changes in ownership, data offers may now properly track the lifetime of a source it represents. Prior to this patch, if an offer with an XWayland source would loose its source, it wouldn't get notified and have an invalid pointer it would potentally crash on. For Wayland sources, an offer would have a weak reference and clean itself up if the source went away. This patch changes so the behavior is consistent, meaning a weak reference is added to the source GObject so that the offer can behave correctly both for Wayland sources and XWayland sources. https://bugzilla.gnome.org/show_bug.cgi?id=750680
2015-06-17 22:25:11 -04:00
wayland/meta-wayland-data-device-private.h \
wayland: Add support for EGLStream client buffers This commit adds for a new type of buffer being attached to a Wayland surface: buffers from an EGLStream. These buffers behave very differently from regular Wayland buffers; instead of each buffer reperesenting an actual frame, the same buffer is attached over and over again, and EGL API is used to switch the content of the OpenGL texture associated with the buffer attached. It more or less side-tracks the Wayland buffer handling. It is implemented by creating a MetaWaylandEglStream object, dealing with the EGLStream state. The lifetime of the MetaWaylandEglStream is tied to the texture object (CoglTexture), which is referenced-counted and owned by both the actors and the MetaWaylandBuffer. When the buffer is reattached and committed, the EGLStream is triggered to switch the content of the associated texture to the new content. This means that one cannot keep old texture content around without copying, so any feature relying on that will effectively be broken. https://bugzilla.gnome.org/show_bug.cgi?id=773629
2016-10-20 03:59:09 -04:00
wayland/meta-wayland-egl-stream.c \
wayland/meta-wayland-egl-stream.h \
wayland: Add common object for device classes Add a new object class, MetaWaylandInputDevice, and make all device classes (pointer, keyboard, touch) inherit it. In the future common functionality may be placed there. https://bugzilla.gnome.org/show_bug.cgi?id=771305
2016-09-12 11:17:28 -04:00
wayland/meta-wayland-input-device.c \
wayland/meta-wayland-input-device.h \
wayland: Implement wl_pointer_gestures The global wl_pointer_gestures object is now created, effectively bridging pinch/swipe gestures with clients, so they're now accessible to clients implementing the protocol.
2015-07-22 10:50:20 -04:00
wayland/meta-wayland-pointer-gestures.c \
wayland/meta-wayland-pointer-gestures.h \
wayland: Implement the wl_pointer_gesture_swipe interface The swipe gesture resources are part of the MetaWaylandPointerClient, which will be used during the emission of CLUTTER_TOUCHPAD_SWIPE events.
2015-07-22 10:43:25 -04:00
wayland/meta-wayland-pointer-gesture-swipe.c \
wayland/meta-wayland-pointer-gesture-swipe.h \
wayland: Implement the wl_pointer_gesture_pinch interface The pinch gesture resources are part of the MetaWaylandPointerClient, which will be used during the propagation of CLUTTER_TOUCHPAD_PINCH events.
2015-07-22 10:46:55 -04:00
wayland/meta-wayland-pointer-gesture-pinch.c \
wayland/meta-wayland-pointer-gesture-pinch.h \
wayland: Add basic input support This copies the basic input support from the Clayland demo compositor. It adds a basic wl_seat implementation which can convert Clutter mouse events to Wayland events. For this to work all of the wayland surface actors need to be made reactive. The wayland keyboard input focus surface is updated whenever Mutter sees a FocusIn event so that it will stay in synch with whatever surface Mutter wants as the focus. Wayland surfaces don't get this event so for now it will just give them focus whenever they are clicked as a hack to test the code. Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2013-05-03 13:51:22 -04:00
wayland/meta-wayland-keyboard.c \
wayland/meta-wayland-keyboard.h \
wayland/meta-wayland-pointer.c \
wayland/meta-wayland-pointer.h \
Implement support for the wp_pointer_constraints protocol The wp_pointer_constraints protocol is a protocol which enables clients to manipulate the behavior of the pointer cursor associated with a seat. Currently available constraints are locking the pointer to a static position, and confining the pointer to a given region. Currently locking is fully implemented, and confining is implemented for rectangular confinement regions. What else is lacking is less troublesome semantics for enabling the lock or confinement; currently the only requirement implemented is that the window that appears focused is the one that may aquire the lock. This means that a pointer could be 'stolen' by creating a new window that receives active focus, or when using focus-follows-mouse, a pointer passes a window that has requested a lock. This semantics can be changed and the protocol itself allows any semantics as seems fit. https://bugzilla.gnome.org/show_bug.cgi?id=744104
2015-06-17 00:10:52 -04:00
wayland/meta-wayland-pointer-constraints.c \
wayland/meta-wayland-pointer-constraints.h \
wayland/meta-pointer-lock-wayland.c \
wayland/meta-pointer-lock-wayland.h \
wayland/meta-pointer-confinement-wayland.c \
wayland/meta-pointer-confinement-wayland.h \
wayland: Move out popup logic to its own file We'll want to expose popup logic outside of meta-wayland-pointer.c and one day we'll also probably want to add touch support for popups, so lets move it to its own file. There are no significant semantical changes, only refactoring. https://bugzilla.gnome.org/show_bug.cgi?id=744452
2015-02-11 04:34:15 -05:00
wayland/meta-wayland-popup.c \
wayland/meta-wayland-popup.h \
wayland: Add basic input support This copies the basic input support from the Clayland demo compositor. It adds a basic wl_seat implementation which can convert Clutter mouse events to Wayland events. For this to work all of the wayland surface actors need to be made reactive. The wayland keyboard input focus surface is updated whenever Mutter sees a FocusIn event so that it will stay in synch with whatever surface Mutter wants as the focus. Wayland surfaces don't get this event so for now it will just give them focus whenever they are clicked as a hack to test the code. Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2013-05-03 13:51:22 -04:00
wayland/meta-wayland-seat.c \
wayland: Add an actor for the cursor When running Mutter under Cogl's KMS backend no cursor will be provided so instead this makes it so the cursor will be painted as a CoglTexture that gets moved in response to mouse motion events. The painting is done in a subclass of ClutterStage so that we can guarantee that the cursor will be painted on top of everything else. This patch adds support for the set_cursor method on the pointer interface so that clients can change the cursor image. The set_pointer method sets a surface and a hotspot position to use for the cursor image. The surface's buffer is converted to a CoglTexture and attached to a pipeline to paint directly via Cogl. If a new buffer is attached to the surface the image will be updated. The cursor reverts back to the default image whenever to the pointer focus is moved off of any surface. The image for the pointer is taken from X. It gets installed into a fixed data location for mutter.
2012-01-18 18:03:23 -05:00
wayland/meta-wayland-seat.h \
wayland: Add MetaWaylandTablet This (very basic at the moment) struct keeps server-side information for wl_tablet resources.
2015-01-09 11:20:22 -05:00
wayland/meta-wayland-tablet.c \
wayland/meta-wayland-tablet.h \
wayland: Add MetaWaylandTabletManager This struct keeps the server side information for the wl_tablet_manager global resource. It keeps the clients requesting this interface, and does keep track of the plugged tablet devices, so wl_tablet_manager.device_added is emitted on the expected clients.
2015-01-09 11:23:17 -05:00
wayland/meta-wayland-tablet-manager.c \
wayland/meta-wayland-tablet-manager.h \
wayland: Add MetaWaylandTabletSeat This object groups all the tablets/tools pertaining to a given seat.
2015-10-27 10:28:10 -04:00
wayland/meta-wayland-tablet-seat.c \
wayland/meta-wayland-tablet-seat.h \
wayland: Add MetaWaylandTabletTool This struct holds the server-side information of a wl_tablet_tool, which represents an specific tool of an specific tablet, and is unique as such.
2015-02-04 12:19:08 -05:00
wayland/meta-wayland-tablet-tool.c \
wayland/meta-wayland-tablet-tool.h \
wayland: Implement wp_tablet_pad This object represents the collection of buttons, strips and rings in a tablet pad. All the objects created (pad, strips and rings) share a common focus surface and have the same lifetime.
2016-05-10 11:14:13 -04:00
wayland/meta-wayland-tablet-pad.c \
wayland/meta-wayland-tablet-pad.h \
wayland: Implement wp_tablet_pad_group
2016-06-22 08:45:43 -04:00
wayland/meta-wayland-tablet-pad-group.c \
wayland/meta-wayland-tablet-pad-group.h \
wayland: Implement wp_tablet_pad_ring This object represents pad "wheels"
2016-05-10 11:10:25 -04:00
wayland/meta-wayland-tablet-pad-ring.c \
wayland/meta-wayland-tablet-pad-ring.h \
wayland: Implement wp_tablet_pad_strip This represents pad sliders.
2016-05-10 11:12:08 -04:00
wayland/meta-wayland-tablet-pad-strip.c \
wayland/meta-wayland-tablet-pad-strip.h \
wayland: Implement the server side bits of wl_touch_interface Clutter touch events are translated into events being sent down the interface resource, with the exception of FRAME/CANCEL events, which are handled directly via an evdev event filter. The seat now announces invariably the WL_SEAT_CAPABILITY_TOUCH capability, this should be eventually updated as devices come and go. The creation of MetaWaylandTouchSurface structs is dynamic, attached to the lifetime of first/last touch on the client surface, and only if the surface requests the wl_touch interface. MetaWaylandTouchInfo structs are created to track individual touches, and are locked to a single MetaWaylandTouchSurface (the implicit grab surface) determined on CLUTTER_TOUCH_BEGIN. https://bugzilla.gnome.org/show_bug.cgi?id=724442
2014-04-24 08:50:47 -04:00
wayland/meta-wayland-touch.c \
wayland/meta-wayland-touch.h \
Move surface state tracking and surface interface to a separate file Move everything surface related from meta-wayland.c to meta-wayland-surface.c https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 12:26:18 -04:00
wayland/meta-wayland-surface.c \
wayland: split headers and distribute structure definitions Instead of having all structures in one huge headers, move them in the appropriate place, and create one header for surface state. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 12:03:30 -04:00
wayland/meta-wayland-surface.h \
wayland: Refactor MetaWaylandSurfaceRoleCursor Move into a standalone meta-wayland-surface-role-cursor.[ch], and make generic enough to work for pointe and additional (eg. tablet) cursors. Most notably, the sprite is now kept completely internal to the cursor role, and updates are routed through the given MetaCursorRenderer (which may be the default one for the pointer, or something else). The way cursor updates after cursor surface destruction has also been reworked, the pointer will just keep track of the last cursor surface, so older surfaces being destroyed don't trigger pointer rechecks/updates.
2015-10-21 10:36:44 -04:00
wayland/meta-wayland-surface-role-cursor.c \
wayland/meta-wayland-surface-role-cursor.h \
wayland: Add MetaWaylandSurfaceRoleTabletCursor This is a simple subclass of MetaWaylandSurfaceRoleCursor, mostly so we can distinguish by GType, the methods in the parent class still apply and are useful.
2016-05-12 09:56:12 -04:00
wayland/meta-wayland-surface-role-tablet-cursor.c \
wayland/meta-wayland-surface-role-tablet-cursor.h \
wayland: split headers and distribute structure definitions Instead of having all structures in one huge headers, move them in the appropriate place, and create one header for surface state. https://bugzilla.gnome.org/show_bug.cgi?id=707128
2013-08-30 12:03:30 -04:00
wayland/meta-wayland-types.h \
wayland: use symbolic constants for interface version Replace magic numbers scattered around the code with proper macros collected in one header file. https://bugzilla.gnome.org/show_bug.cgi?id=707851
2013-09-10 07:45:27 -04:00
wayland/meta-wayland-versions.h \
wayland: Split outputs to another file
2014-04-22 18:03:40 -04:00
wayland/meta-wayland-outputs.c \
wayland/meta-wayland-outputs.h \
wayland: Add support for the xdg-foreign protocol This commits adds support for exporting xdg_surface handles via xdg_exporter and importing them via xdg_importer. This bumps the required wayland-protocols version to 1.6. https://bugzilla.gnome.org/show_bug.cgi?id=769786
2015-09-23 20:05:25 -04:00
wayland/meta-wayland-xdg-foreign.c \
wayland/meta-wayland-xdg-foreign.h \
window-wayland.[ch] => meta-window-wayland.[ch] This finishes off the meta- prefix for wayland/.
2015-04-27 21:09:16 -04:00
wayland/meta-window-wayland.c \
wayland/meta-window-wayland.h \
wayland: Split out shell surface code from meta-wayland-surface.c Move xdg_shell related functionality to a new meta-wayland-xdg-shell.c and wl_shell related functionality to a new meta-wayland-wl-shell.c, and adapt role object tree. Common functionality related to the surface being drawn as a MetaSurfaceActor was moved to a MetaWaylandSurfaceRoleActorSurface role. The subsurface role GObject is made to inherit the actor surface GObject. Shell surface hooks (configure, ping, close, popup done) were added to a MetaWaylandSurfaceRoleShellSurface GObject which inherits the surface actor role GObject. The shell surface roles (xdg_surface, xdg_popup, wl_shell_surface) are made to inherit the shell surface GObject and implement the relevant API. https://bugzilla.gnome.org/show_bug.cgi?id=757623 https://bugzilla.gnome.org/show_bug.cgi?id=763431
2015-12-14 23:51:24 -05:00
wayland/meta-wayland-xdg-shell.c \
wayland/meta-wayland-xdg-shell.h \
wayland/meta-wayland-wl-shell.c \
wayland/meta-wayland-wl-shell.h \
wayland: Move out gtk_shell from meta-wayland-surface.c https://bugzilla.gnome.org/show_bug.cgi?id=769936
2016-06-27 22:05:55 -04:00
wayland/meta-wayland-gtk-shell.c \
wayland/meta-wayland-gtk-shell.h \
wayland: add keyboard shortcuts inhibitor protocol https://bugzilla.gnome.org/show_bug.cgi?id=783342
2017-03-21 06:47:16 -04:00
wayland/meta-wayland-inhibit-shortcuts.c \
wayland/meta-wayland-inhibit-shortcuts.h \
wayland: use the inhibit shortcuts dialog Plug the new MetaInhbitShortcutsDialog to the relevant Wayland protocol implementation. Also, remember the last user choice for a given surface to avoid asking continuously the same question. https://bugzilla.gnome.org/show_bug.cgi?id=783342
2017-06-14 05:27:14 -04:00
wayland/meta-wayland-inhibit-shortcuts-dialog.c \
wayland/meta-wayland-inhibit-shortcuts-dialog.h \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
$(NULL)
Conditionalize Wayland support again
2014-08-13 20:19:35 -04:00
endif
wayland: Adds basic hybrid X + Wayland support This adds support for running mutter as a hybrid X and Wayland compositor. It runs a headless XWayland server for X applications that presents wayland surfaces back to mutter which mutter can then composite. This aims to not break Mutter's existing support for the traditional X compositing model which means a single build of Mutter can be distributed supporting the traditional model and the new Wayland based compositing model. TODO: although building with --disable-wayland has at least been tested, I still haven't actually verified that running as a traditional compositor isn't broken currently. Note: At this point no input is supported Note: multiple authors have contributed to this patch: Authored-by: Robert Bragg <robert@linux.intel.com> Authored-by: Neil Roberts <neil@linux.intel.com> Authored-by: Rico Tzschichholz. Authored-by: Giovanni Campagna <gcampagna@src.gnome.org>
2012-01-07 17:21:32 -05:00
Make the native backend build-optional
2014-05-29 12:11:26 -04:00
if HAVE_NATIVE_BACKEND
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
libmutter_@LIBMUTTER_API_VERSION@_la_SOURCES += \
Make the native backend build-optional
2014-05-29 12:11:26 -04:00
backends/native/meta-backend-native.c \
backends/native/meta-backend-native.h \
backends/native: Implement support for pointer barriers When running as a dispay server pointer barriers are a server side feature and requires no client interaction of any sort. This patch implements pointer barriers that can be used when running as a display server on the native backend. Running as a display server using the X11 backend is currently not supported. https://bugzilla.gnome.org/show_bug.cgi?id=706655
2015-01-16 03:50:51 -05:00
backends/native/meta-backend-native-private.h \
backends/native/meta-barrier-native.c \
backends/native/meta-barrier-native.h \
backends/native: Move CRTC code to its own file Move code dealing with MetaCrtcKms and related functionality to its own file. Eventually, MetaCrtcKms should become a GObject based on MetaCrtc, and this commit is in preparation for that. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-07-04 04:04:39 -04:00
backends/native/meta-crtc-kms.c \
backends/native/meta-crtc-kms.h \
Make mutter manage its own clutter backends Introduce two new clutter backends: MetaClutterBackendX11 and MetaClutterBackendNative. They are so far only wrap ClutterBackendX11 and ClutterBackendEglNative respectively, but the aim is to move things from the original clutter backends when needed. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-04 04:19:23 -04:00
backends/native/meta-clutter-backend-native.c \
backends/native/meta-clutter-backend-native.h \
Make the native backend build-optional
2014-05-29 12:11:26 -04:00
backends/native/meta-cursor-renderer-native.c \
backends/native/meta-cursor-renderer-native.h \
monitor-manager-kms: Add common modes Some output devices only advertise their preferred mode even though they're able to display others too. This means we can include some common modes in each output's supported list. This is particularly important for mirroring, since we can only mirror outputs which are using the same resolution. https://bugzilla.gnome.org/show_bug.cgi?id=744544
2015-02-14 15:03:38 -05:00
backends/native/meta-default-modes.h \
backends: Split out CRTC/output management to MetaGpu In order to eventually support multilpe GPUs with their own connectors, split out related meta data management (i.e. outputs, CRTCs and CRTC modes) into a new MetaGpu GObject. The Xrandr backend always assumes there is always only a single "GPU" as the GPU is abstracted by the X server; only the native backend (aside from the test backend) will eventually see more than one GPU. The Xrandr backend still moves some management to MetaGpuXrandr, in order to behave more similarly to the KMS counterparts. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-07-10 06:19:32 -04:00
backends/native/meta-gpu-kms.c \
backends/native/meta-gpu-kms.h \
Make the native backend build-optional
2014-05-29 12:11:26 -04:00
backends/native/meta-idle-monitor-native.c \
backends/native/meta-idle-monitor-native.h \
backends/native: Add libinput-based MetaInputSettings implementation The libinput_device is fetched from the ClutterInputDevice, and configured through the libinput_device_*config* API. https://bugzilla.gnome.org/show_bug.cgi?id=739397
2014-10-29 10:42:32 -04:00
backends/native/meta-input-settings-native.c \
backends/native/meta-input-settings-native.h \
Make the native backend build-optional
2014-05-29 12:11:26 -04:00
backends/native/meta-monitor-manager-kms.c \
backends/native/meta-monitor-manager-kms.h \
backends/native/meta-launcher.c \
backends/native/meta-launcher.h \
backends/native: Move output code to its own file Move code dealing with MetaOutputKms and related functionality to its own file. Eventually, MetaOutputKms should become a GObject based on MetaOutput, and this commit is in preparation for that. https://bugzilla.gnome.org/show_bug.cgi?id=785381
2017-07-04 00:11:44 -04:00
backends/native/meta-output-kms.c \
backends/native/meta-output-kms.h \
Introduce MetaRenderer MetaRenderer is meant to be the object responsible for rendering the scene graph. It will contain the logic related to the cogl winsys backend, the clutter backend, and the clutter stage window. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-07 11:07:46 -04:00
backends/native/meta-renderer-native.c \
backends/native/meta-renderer-native.h \
Explicitly create per backend stage windows Split the stage window implementations into three separate objects: one for X11 as a compositing manager, one for X11 running as a nested Wayland compositor, and one for running with the native backend. The new stage window implementations are only thin shells; this is in preparation for making the stage windows behave more differently. https://bugzilla.gnome.org/show_bug.cgi?id=768976
2016-05-20 03:58:10 -04:00
backends/native/meta-stage-native.c \
backends/native/meta-stage-native.h \
Make the native backend build-optional
2014-05-29 12:11:26 -04:00
backends/native/dbus-utils.c \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
backends/native/dbus-utils.h \
$(NULL)
Make the native backend build-optional
2014-05-29 12:11:26 -04:00
endif
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
nodist_libmutter_@LIBMUTTER_API_VERSION@_la_SOURCES = $(mutter_built_sources)
Kill HAVE_WAYLAND
2014-02-17 21:28:41 -05:00
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
libmutter_@LIBMUTTER_API_VERSION@_la_LDFLAGS = \
-no-undefined -export-symbols-regex "^(meta|ag)_.*"
libmutter_@LIBMUTTER_API_VERSION@_la_LIBADD = \
Fix the merged build https://bugzilla.gnome.org/show_bug.cgi?id=760439
2016-04-08 13:58:20 -04:00
$(MUTTER_LIBS) \
$(MUTTER_NATIVE_BACKEND_LIBS) \
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
$(top_builddir)/clutter/clutter/libmutter-clutter-$(LIBMUTTER_API_VERSION).la \
Fix the merged build https://bugzilla.gnome.org/show_bug.cgi?id=760439
2016-04-08 13:58:20 -04:00
$(NULL)
call AC_LIBTOOL_WIN32_DLL. * configure.in: call AC_LIBTOOL_WIN32_DLL. * src/Makefile.am: add -no-undefined to libmetacity_private_la_LDFLAGS and write dependency libraries in libmetacity_private_la_LIBADD.
2003-04-19 03:19:04 -04:00
Fix confusion about MetaPreview in introspection build MetaPreview is only built into libmutter-private, and not included in the mutter executable. Linking mutter against libmutter-private was inadvertently added when the introspection build process was set up, but isn't actually needed, and if -Wl,-as-needed is added during the build process, then the libmutter-private dependency will be skipped. * Don't link mutter (or the test programs) against libmutter-private * Exclude meta-preview.h from the set of headers we feed into the introspection build process Reported by Patryk Zawadzki http://bugzilla.gnome.org/show_bug.cgi?id=587975
2009-07-17 07:51:21 -04:00
# Headers installed for plugins; introspected information will
# be extracted into Mutter-<version>.gir
meta: Add generated meta-version.h Avoid populating *_VERSION constants through cflags in pkg-config-file which could be overridden by the project using it. Properly prefix the defines with META_ to make gi-scanner happy.
2014-06-05 08:05:16 -04:00
libmutterinclude_headers = \
barrier: Add a new Meta wrapper for pointer barriers Currently, we have a few function wrappers in the shell for pointer barriers. If we want to implement interactive features on barriers, we need some sort of signal to be notified of the interactivity. In that case, we need to make a more sophisticated object-based wrapper for a pointer barrier. Add one, and stick it in mutter. https://bugzilla.gnome.org/show_bug.cgi?id=677215
2012-07-30 14:54:03 -04:00
meta/barrier.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/boxes.h \
meta/common.h \
meta/compositor-mutter.h \
meta/compositor.h \
meta/display.h \
meta/errors.h \
Revert "Move MetaGroup to be X11-specific" This reverts commit f940292cfe5a80290a5dae8a62e05fbcbab32a7f. Turns out MetaGroup was public API and was used by gnome-shell. Ugh.
2014-03-19 09:11:23 -04:00
meta/group.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/keybindings.h \
meta/main.h \
backends: Make MetaBackend available to introspection This moves meta-backend.h under meta/ and, for now, just exposes to introspection the methods that we actually need in gnome-shell. https://bugzilla.gnome.org/show_bug.cgi?id=734301
2014-08-05 08:11:59 -04:00
meta/meta-backend.h \
Rewrite background code The old requirement that multiple MetaBackgroundActor objects be layered on top of each to produce blended backgrounds resulted in extremely inefficient drawing since the entire framebuffer had to be read and written multiple times. * Replace the MetaBackground ClutterContent with a plain GObject that serves to hold the background parameters and prerender textures to be used to draw the background. It handles colors, gradients, and blended images, but does not handle vignetting * Add vignetting to MetaBackgroundActor directly. * Add MetaBackgroundImage and MetaBackgroundImageCache to allow multiple MetaBackground objects to share the same images By removing the usage of ClutterContent, the following optimizations were easy to add: Blending is turned off when the actor is fully opaque Nearest-neighbour filtering is used when drawing 1:1 The GLSL vignette code is slightly improved to use a vertex shader snippet for computing the texture coordinate => position in actor mapping. https://bugzilla.gnome.org/show_bug.cgi?id=735637
2014-08-10 11:26:14 -04:00
meta/meta-background.h \
MetaBackgroundActor: make it a public class https://bugzilla.gnome.org/show_bug.cgi?id=656433
2011-08-28 21:20:29 -04:00
meta/meta-background-actor.h \
Rewrite background code The old requirement that multiple MetaBackgroundActor objects be layered on top of each to produce blended backgrounds resulted in extremely inefficient drawing since the entire framebuffer had to be read and written multiple times. * Replace the MetaBackground ClutterContent with a plain GObject that serves to hold the background parameters and prerender textures to be used to draw the background. It handles colors, gradients, and blended images, but does not handle vignetting * Add vignetting to MetaBackgroundActor directly. * Add MetaBackgroundImage and MetaBackgroundImageCache to allow multiple MetaBackground objects to share the same images By removing the usage of ClutterContent, the following optimizations were easy to add: Blending is turned off when the actor is fully opaque Nearest-neighbour filtering is used when drawing 1:1 The GLSL vignette code is slightly improved to use a vertex shader snippet for computing the texture coordinate => position in actor mapping. https://bugzilla.gnome.org/show_bug.cgi?id=735637
2014-08-10 11:26:14 -04:00
meta/meta-background-image.h \
compositor: rework how backgrounds are managed Background handling in GNOME is very roundabout at the moment. gnome-settings-daemon uses gnome-desktop to read the background from disk into a screen-sized pixmap. It then sets the XID of that pixmap on the _XROOTPMAP_ID root window property. mutter puts that pixmap into a texture/actor which gnome-shell then uses. Having the gnome-settings-daemon detour from disk to screen means we can't easily let the compositor handle transition effects when switching backgrounds. Also, having the background actor be per-screen instead of per-monitor means we may have oversized textures in certain multihead setups. This commit changes mutter to read backgrounds from disk itself, and it changes backgrounds to be per-monitor. This way background handling/compositing is left to the compositor. https://bugzilla.gnome.org/show_bug.cgi?id=682427
2013-01-23 15:54:41 -05:00
meta/meta-background-group.h \
core: Add MetaCloseDialog This is an interface that can be used to implement the "application is not responding" dialog. One instance is created per window, which is initially hidden, and can be shown/hidden on demand. https://bugzilla.gnome.org/show_bug.cgi?id=711619
2016-07-11 07:07:46 -04:00
meta/meta-close-dialog.h \
core: add MetaInhibitShortcutsDialog Add a new interface for allowing or denying shortcuts inhibit requests. https://bugzilla.gnome.org/show_bug.cgi?id=783342
2017-06-14 04:54:16 -04:00
meta/meta-inhibit-shortcuts-dialog.h \
Add MetaCursorTracker, a new helper for tracking the cursor sprite Under X, we need to use XFixes to watch the cursor changing, while on wayland, we're in charge of setting and painting the cursor. MetaCursorTracker provides the abstraction layer for gnome-shell, which can thus drop ShellXFixesCursor. In the future, it may grow the ability to watch for pointer position too, especially if CursorEvents are added to the next version of XInput2, and thus it would also replace the PointerWatcher we use for gnome-shell's magnifier. https://bugzilla.gnome.org/show_bug.cgi?id=705911
2013-08-13 06:57:41 -04:00
meta/meta-cursor-tracker.h \
dnd: Implement MetaDnd Implement MetaDnd for emitting DnD signals to plugins such as gnome-shell. The xdnd handling code comes from gnome-shell, and it is hidden behind MetaDnd now. https://bugzilla.gnome.org/show_bug.cgi?id=765003
2017-01-02 09:11:32 -05:00
meta/meta-dnd.h \
Add a new helper for tracking user idle activity When running as a wayland compositor, we can't use the xserver's IDLETIME, because that's updated only in response to X events. But we have all the events ourselves, so we can just run the timer in process. https://bugzilla.gnome.org/show_bug.cgi?id=706005
2013-08-14 06:50:48 -04:00
meta/meta-idle-monitor.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/meta-plugin.h \
monitor-manager: Expose MetaMonitorManager to introspection This just exposes the type and the singleton getter necessary to make it available to introspection. We'll expose more functionality as it becomes needed. https://bugzilla.gnome.org/show_bug.cgi?id=743745
2015-01-30 08:51:18 -05:00
meta/meta-monitor-manager.h \
backend: Move settings into a new MetaSettings object Introduce MetaSettings and add the settings managed by MetaBackend into the new object. These settings include: experimental-features and UI scaling factor. https://bugzilla.gnome.org/show_bug.cgi?id=777732
2017-04-21 04:40:51 -04:00
meta/meta-settings.h \
MetaShapedTexture: Make public and directly derive from ClutterActor ClutterTexture has many features that we simply don't use and don't make sense for a subclass with custom drawing. Deriving directly from ClutterActor simplifies our code by avoiding workarounds and makes things more robust. Additionally, make it public. GNOME Shell was already assuming that any MetaShapedTexture was also a ClutterTexture, and we need to replace these bits with new API for GNOME Shell to use. https://bugzilla.gnome.org/show_bug.cgi?id=660941
2011-10-04 17:35:11 -04:00
meta/meta-shaped-texture.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/meta-shadow-factory.h \
meta/meta-window-actor.h \
compositor: Export meta_shadow_factory_get_shadow to introspection I forgot we had a separate list of headers for introspection to scan.
2015-07-06 03:27:03 -04:00
meta/meta-window-shape.h \
Move the installed includes to a subdir If mutter is going to be a "real" library, then it should install its includes so that users can do #include <meta/display.h> rather than #include <display.h> So rename the includedir accordingly, move src/include to src/meta, and fix up all internal references. There were a handful of header files in src/include that were not installed; this appears to have been part of a plan to keep core/, ui/, and compositor/ from looking at each others' private includes, but that wasn't really working anyway. So move all non-installed headers back into core/ or ui/. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 19:29:12 -05:00
meta/prefs.h \
meta/screen.h \
meta/theme.h \
meta/types.h \
meta/util.h \
meta/window.h \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
meta/workspace.h \
$(NULL)
add a pc file for libmetacity-private Thu Nov 7 17:07:21 2002 Jonathan Blandford <jrb@redhat.com> * src/libmetacity-private.pc.in: add a pc file for libmetacity-private * src/Makefile.am: Install a few files as a shared library so that others can draw metacity themes.
2002-11-07 17:09:59 -05:00
meta: Add generated meta-version.h Avoid populating *_VERSION constants through cflags in pkg-config-file which could be overridden by the project using it. Properly prefix the defines with META_ to make gi-scanner happy.
2014-06-05 08:05:16 -04:00
libmutterinclude_built_headers = \
Install enum types
2015-07-06 00:58:45 -04:00
meta/meta-version.h \
meta/meta-enum-types.h \
$(NULL)
meta: Add generated meta-version.h Avoid populating *_VERSION constants through cflags in pkg-config-file which could be overridden by the project using it. Properly prefix the defines with META_ to make gi-scanner happy.
2014-06-05 08:05:16 -04:00
libmutterinclude_base_headers = \
$(libmutterinclude_headers) \
$(libmutterinclude_built_headers)
Revert "wayland: make parallel installable with regular mutter" This reverts commit ea3d2b4759524345c89fe08ad0c159d7136dbdf1.
2014-04-09 18:12:50 -04:00
libmutterincludedir = $(includedir)/mutter/meta
build: Only install libmutter-private for GTK3 builds Define INSTALL_LIBMUTTER_PRIVATE with AM_CONDITIONAL and use it to build an installed or uninstalled libmutter-private.so https://bugzilla.gnome.org/show_bug.cgi?id=630203
2010-09-23 08:32:48 -04:00
Comprehensively rename to Mutter Code: All references in the code not related to themes, keybindings, or GConf were changed from 'metacity' to 'mutter'. This includes, among other things, strings, comments, the atoms used in the message protocol, and the envvars used for debugging. The GConf schema file was reduced to the 3 settings new to mutter. The overall version was brought up to 2.27 to match current gnome. Structure: All files named '*metacity*' were renamed '*mutter*' with appropriate changes in the automake system. Files removed are doc/creating_themes, src/themes, doc/metacity-theme.dtd, metacity.doap. These files will eventually end up in an external gnome-wm-data module. Installation location: On the filesystem the mutter-plugindir was change from $(libdir)/metacity/plugins/clutter to just $(libdir)/mutter/plugins. The mutter-plugins.pc.in reflects these changes. Note: mutter.desktop.in and mutter-wm.desktop both continue to have X-GNOME-WMSettingsModule=metacity set. This allows gnome-control-center to continue using libmetacity.so for configuration. This is fine since most the general keybindings and wm settings are being read from /apps/metacity/* in gconf.
2009-06-10 06:29:20 -04:00
libmutterinclude_HEADERS = \
Move atomnames.h to x11/ This should *not* be part of the public API.
2015-04-27 19:36:46 -04:00
$(libmutterinclude_headers)
Build and install introspection information Build a XML gir file and binary typelib file for the interfaces that we are installing for plugin use. They are installed into $(pkglibdir) since they are private to the application. http://bugzilla.gnome.org/show_bug.cgi?id=580041
2008-11-01 13:40:29 -04:00
meta: Add generated meta-version.h Avoid populating *_VERSION constants through cflags in pkg-config-file which could be overridden by the project using it. Properly prefix the defines with META_ to make gi-scanner happy.
2014-06-05 08:05:16 -04:00
nodist_libmutterinclude_HEADERS = \
$(libmutterinclude_built_headers)
Revert "wayland: make parallel installable with regular mutter" This reverts commit ea3d2b4759524345c89fe08ad0c159d7136dbdf1.
2014-04-09 18:12:50 -04:00
bin_PROGRAMS=mutter
Add a test framework and stacking tests Add a basic framework for tests of Mutter handling of client behavior; mutter-test-runner is a Mutter-based compositor that forks off instances of mutter-test-client and sends commands to them based on scripts. The scripts also include assertions. mutter-test-runner always runs in nested-Wayland mode since the separate copy of Xwayland is helpful in giving a reliably clean X server to test against. Initially the commands and assertions are designed to test the stacking behavior of Mutter, but the framework should be extensible to test other parts of client behavior like focus. The tests are installed according to: https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests if --enable-installed-tests is passed to configure. You can run them uninstalled with: cd src && make run-tests (Not in 'make check' to avoid breaking 'make distcheck' if Mutter can't be run nested.) https://bugzilla.gnome.org/show_bug.cgi?id=736505
2014-09-11 13:43:32 -04:00
noinst_PROGRAMS=
Make the bindings in src/core/*-bindings.h generate GConf schemas too. 2008-10-12 Thomas Thurman <tthurman@gnome.org> Make the bindings in src/core/*-bindings.h generate GConf schemas too. Note that there's an i18n issue (documented in schema-bindings.c) which will be fixed next checkin. * src/core/schema-bindings.c: major fixup to make it ready for use as part of the actual build process. * src/Makefile.am: added magic to make it call schema-bindings after it builds it. * src/core/window-bindings.h: added comments; also, window menu was listed variously as alt-Space and alt-Print; it should have been alt-Space. * src/metacity.schemas.in.in: renamed from s/\.in$//, sentinel added for the generated bindings, warning at the top now untrue, and removed. svn path=/trunk/; revision=3952
2008-10-12 19:29:09 -04:00
Revert "wayland: make parallel installable with regular mutter" This reverts commit ea3d2b4759524345c89fe08ad0c159d7136dbdf1.
2014-04-09 18:12:50 -04:00
mutter_SOURCES = core/mutter.c
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
mutter_LDADD = $(MUTTER_LIBS) libmutter-@LIBMUTTER_API_VERSION@.la
Allow mutter to be used as a library Move all of the mutter code into a new libmutter-wm.so, split its main() method into meta_get_option_context(), meta_init() and meta_run(), add methods for using in-process plugins, and add libmutter-wm.pc pointing to the new library. The mutter binary is now just a tiny program that links against libmutter-wm. The --version and --mutter-plugins options are handled at the mutter level, not in libmutter-wm, and a few strange unused command-line options (--no-force-fullscreen and --no-tab-popup) have been removed. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 16:16:26 -05:00
Add a framework for restarting the compositor with nice visuals The current GNOME Shell Alt-F2 restart looks very messy and also provides no indication to the user what is going on. We need to restart the compositor to switch in and out of stereo mode, so add a framework for doing this more cleanly: Additions: meta_restart(): restarts the compositor with a message MetaDisplay::show-restart-message: signal the embedding shell to show a message MetaDisplay::restart: signal the embedding shell to restart itself. meta_is_restart(): indicates whether the current instance is a restart so we can suppress login animations. A helper program meta-restart-helper holds the composite overlay window up during the restart to avoid visual artifacts. https://bugzilla.gnome.org/show_bug.cgi?id=733026
2014-05-08 18:35:49 -04:00
libexec_PROGRAMS = mutter-restart-helper
mutter_restart_helper_SOURCES = core/restart-helper.c
mutter_restart_helper_LDADD = $(MUTTER_LIBS)
Add a test framework and stacking tests Add a basic framework for tests of Mutter handling of client behavior; mutter-test-runner is a Mutter-based compositor that forks off instances of mutter-test-client and sends commands to them based on scripts. The scripts also include assertions. mutter-test-runner always runs in nested-Wayland mode since the separate copy of Xwayland is helpful in giving a reliably clean X server to test against. Initially the commands and assertions are designed to test the stacking behavior of Mutter, but the framework should be extensible to test other parts of client behavior like focus. The tests are installed according to: https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests if --enable-installed-tests is passed to configure. You can run them uninstalled with: cd src && make run-tests (Not in 'make check' to avoid breaking 'make distcheck' if Mutter can't be run nested.) https://bugzilla.gnome.org/show_bug.cgi?id=736505
2014-09-11 13:43:32 -04:00
include Makefile-tests.am
Use standard introspection configure/Makefile bits This changes the introspection configure flag from --with/--without-introspection to --enable/--disable-introspection, and changes it so that trying to enable introspection when g-i is not installed results in an error, rather than being silently ignored. https://bugzilla.gnome.org/show_bug.cgi?id=643959
2011-03-05 15:01:33 -05:00
if HAVE_INTROSPECTION
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
include $(INTROSPECTION_MAKEFILE)
Build and install introspection information Build a XML gir file and binary typelib file for the interfaces that we are installing for plugin use. They are installed into $(pkglibdir) since they are private to the application. http://bugzilla.gnome.org/show_bug.cgi?id=580041
2008-11-01 13:40:29 -04:00
# These files are in package-private directories, even though they may be used
# by plugins. If you're writing a plugin, use g-ir-compiler --add-include-path
# and g-ir-compiler --includedir.
girdir = $(pkglibdir)
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
gir_DATA = Meta-$(LIBMUTTER_API_VERSION).gir
Build and install introspection information Build a XML gir file and binary typelib file for the interfaces that we are installing for plugin use. They are installed into $(pkglibdir) since they are private to the application. http://bugzilla.gnome.org/show_bug.cgi?id=580041
2008-11-01 13:40:29 -04:00
typelibdir = $(pkglibdir)
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
typelib_DATA = Meta-$(LIBMUTTER_API_VERSION).typelib
INTROSPECTION_GIRS = Meta-$(LIBMUTTER_API_VERSION).gir
INTROSPECTION_SCANNER_ARGS = \
--add-include-path=$(top_builddir)/clutter/clutter \
--add-include-path=$(top_builddir)/cogl/cogl \
--add-include-path=$(top_builddir)/cogl/cogl-pango \
$(NULL)
INTROSPECTION_COMPILER_ARGS = \
--includedir=$(top_builddir)/clutter/clutter \
--includedir=$(top_builddir)/cogl/cogl \
--includedir=$(top_builddir)/cogl/cogl-pango \
$(NULL)
INTROSPECTION_SCANNER_ENV = \
PKG_CONFIG_PATH=$(top_builddir)/clutter/clutter/:$(top_builddir)/cogl/cogl/:$(top_builddir)/cogl/cogl-pango/:$${PKG_CONFIG_PATH}
Meta-@LIBMUTTER_API_VERSION@.gir: libmutter-$(LIBMUTTER_API_VERSION).la
Meta_@LIBMUTTER_API_VERSION@_gir_VERSION = $(LIBMUTTER_API_VERSION)
Meta_@LIBMUTTER_API_VERSION@_gir_INCLUDES = \
GObject-2.0 \
GDesktopEnums-3.0 \
Gdk-3.0 \
Gtk-3.0 \
Cogl-$(LIBMUTTER_API_VERSION) \
Clutter-$(LIBMUTTER_API_VERSION) \
xlib-2.0 \
xfixes-4.0 \
$(NULL)
Meta_@LIBMUTTER_API_VERSION@_gir_EXPORT_PACKAGES = libmutter-$(LIBMUTTER_API_VERSION)
Meta_@LIBMUTTER_API_VERSION@_gir_CFLAGS = $(AM_CPPFLAGS)
Meta_@LIBMUTTER_API_VERSION@_gir_LIBS = libmutter-$(LIBMUTTER_API_VERSION).la
Meta_@LIBMUTTER_API_VERSION@_gir_FILES = \
$(libmutterinclude_base_headers) \
$(filter %.c,$(libmutter_@LIBMUTTER_API_VERSION@_la_SOURCES) $(nodist_libmutter_@LIBMUTTER_API_VERSION@_la_SOURCES))
Meta_@LIBMUTTER_API_VERSION@_SCANNERFLAGS = --warn-all --warn-error
Build and install introspection information Build a XML gir file and binary typelib file for the interfaces that we are installing for plugin use. They are installed into $(pkglibdir) since they are private to the application. http://bugzilla.gnome.org/show_bug.cgi?id=580041
2008-11-01 13:40:29 -04:00
endif
MetaIdleMonitor: add a DBus interface for the idle monitor To allow other clients (gnome-session, gnome-settings-daemon) to monitor user activity, introduce a DBus interface for the idle monitor inside mutter. https://bugzilla.gnome.org/show_bug.cgi?id=706005
2013-08-14 07:51:05 -04:00
dbus_idle_built_sources = meta-dbus-idle-monitor.c meta-dbus-idle-monitor.h
Fix 'make distcheck' * Make generation of the .gir file work for srcdir != builddir * Add files to CLEANFILES as needed * Don't distribute the generated file mutter.schemas
2009-07-16 17:54:56 -04:00
CLEANFILES = \
$(mutter_built_sources) \
$(typelib_DATA) \
$(gir_DATA)
use the inline image data for default icon 2001-09-17 Havoc Pennington <hp@pobox.com> * src/ui.c: use the inline image data for default icon * src/common.h (META_MINI_ICON_HEIGHT): move icon size defines here * src/Makefile.am: Create an inlinepixbufs.h header with inline images
2001-09-17 00:42:37 -04:00
Don't remove meta/meta-version.h during make clean meta/meta-version.h is generated by configure, so it should be removed with make distclean, not make clean. This is the heuristic described in https://www.gnu.org/software/automake/manual/html_node/Clean.html Cleaning it in make clean means that configure; make clean; make won't work properly as meta/meta-version.h will be removed and not regenerated. https://bugzilla.gnome.org/show_bug.cgi?id=734960
2014-08-17 14:03:09 -04:00
DISTCLEANFILES = \
build: Clean up .pc files
2017-02-15 17:37:21 -05:00
$(libmutterinclude_built_headers) \
$(pkgconfig_DATA)
Don't remove meta/meta-version.h during make clean meta/meta-version.h is generated by configure, so it should be removed with make distclean, not make clean. This is the heuristic described in https://www.gnu.org/software/automake/manual/html_node/Clean.html Cleaning it in make clean means that configure; make clean; make won't work properly as meta/meta-version.h will be removed and not regenerated. https://bugzilla.gnome.org/show_bug.cgi?id=734960
2014-08-17 14:03:09 -04:00
add a pc file for libmetacity-private Thu Nov 7 17:07:21 2002 Jonathan Blandford <jrb@redhat.com> * src/libmetacity-private.pc.in: add a pc file for libmetacity-private * src/Makefile.am: Install a few files as a shared library so that others can draw metacity themes.
2002-11-07 17:09:59 -05:00
pkgconfigdir = $(libdir)/pkgconfig
Make libmutter and friends parallel installable In order to minimize the amount of breakage, while at the same time making it easier to make backward incompatible changes needed to continue turning libmutter into a capable Wayland compositor, make the libmutter and friends (libmutter-clutter, libmutter-cogl*) parallel installable by adding a version number to the name. This changes various filenames, for example what previously was libmutter.so is now libmutter-0.so (assuming the version for now is 0), and libmutter-clutter-1.0.so is now libmutter-clutter-0.so. The pkg-config filenames and GObject introspection has been renamed to reflect this as well. This enables a downstream compositor rely on a specific version of the libmutter API, while gracefully handling API/ABI changes by having to update to the new version at their own pace. https://bugzilla.gnome.org/show_bug.cgi?id=777317
2016-11-25 11:16:07 -05:00
pkgconfig_DATA = libmutter-$(LIBMUTTER_API_VERSION).pc
add a pc file for libmetacity-private Thu Nov 7 17:07:21 2002 Jonathan Blandford <jrb@redhat.com> * src/libmetacity-private.pc.in: add a pc file for libmetacity-private * src/Makefile.am: Install a few files as a shared library so that others can draw metacity themes.
2002-11-07 17:09:59 -05:00
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
EXTRA_DIST += \
$(wayland_protocols) \
libmutter.pc.in \
Install enum types
2015-07-06 00:58:45 -04:00
meta-enum-types.h.in \
meta-enum-types.c.in \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
org.freedesktop.login1.xml \
Rename the DBus interface files
2014-03-31 23:31:42 -04:00
org.gnome.Mutter.DisplayConfig.xml \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
org.gnome.Mutter.IdleMonitor.xml \
Add remote desktop and screen cast functionality This commit adds basic screen casting and remote desktoping functionalty. This works by exposing two D-Bus API services: org.gnome.Mutter.ScreenCast and org.gnome.Mutter.RemoteDesktop. The remote desktop API is used to create remote desktop sessions. For each session, a D-Bus object is created, and an application can manage the session by sending messages to the session object. A remote desktop session the user to emit input events using the D-Bus methods on the session object. To get framebuffer content, the application should create an associated screen cast session. The screen cast API is used to create screen cast sessions. One can so far either create stand-alone screen cast sessions, or a screen cast session associated with a remote desktop session. A remote desktop associated screen cast session is managed by the remote desktop session. So far only remote desktop managed screen cast sessions are implemented. Each screen cast session may have one or more streams. A screen cast stream is a stream of buffers of some part of the compositor content. So far API exists for creating streams of monitors and windows, but only monitor streams are implemented. When a screen cast session is started, the one PipeWire stream is created for each screen cast stream created for the session. When this has happened, a PipeWireStreamAdded signal is emitted on the stream object, passing a unique identifier. The application may use this identifier to find the associated stream being advertised by the PipeWire daemon. The remote desktop and screen cast functionality must be explicitly be enabled at ./configure time by passing --enable-remote-desktop to ./configure. Doing this will build both screen cast and remote desktop support. To actually enable the screen casting and remote desktop, the user must enable the experimental feature. See org.gnome.mutter.experimental-features. https://bugzilla.gnome.org/show_bug.cgi?id=784199
2017-06-21 02:23:44 -04:00
org.gnome.Mutter.RemoteDesktop.xml \
org.gnome.Mutter.ScreenCast.xml \
monitor-manager-kms: Add common modes Some output devices only advertise their preferred mode even though they're able to display others too. This means we can include some common modes in each output's supported list. This is particularly important for mirroring, since we can only mirror outputs which are using the same resolution. https://bugzilla.gnome.org/show_bug.cgi?id=744544
2015-02-14 15:03:38 -05:00
backends/native/gen-default-modes.py \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
$(NULL)
Emit signals when workspaces are added, removed or switched The patch adds GLib marshalling code to Mutter, since it's required for the "workspace-switched" signal. The definition of MetaMotionDirection enum is moved to common.h since it's now used in workspace.c. A little cleaning is done in workspace.c:meta_workspace_activate_with_focus(), where compositor-specific code is merged with the rest of the function (required to emit signal), removing #ifdefs.
2009-07-02 11:19:02 -04:00
Don't remove meta/meta-version.h during make clean meta/meta-version.h is generated by configure, so it should be removed with make distclean, not make clean. This is the heuristic described in https://www.gnu.org/software/automake/manual/html_node/Clean.html Cleaning it in make clean means that configure; make clean; make won't work properly as meta/meta-version.h will be removed and not regenerated. https://bugzilla.gnome.org/show_bug.cgi?id=734960
2014-08-17 14:03:09 -04:00
BUILT_SOURCES = \
$(mutter_built_sources) \
$(libmutterinclude_built_headers)
Install enum types
2015-07-06 00:58:45 -04:00
MUTTER_STAMP_FILES = stamp-meta-enum-types.h
Emit signals when workspaces are added, removed or switched The patch adds GLib marshalling code to Mutter, since it's required for the "workspace-switched" signal. The definition of MetaMotionDirection enum is moved to common.h since it's now used in workspace.c. A little cleaning is done in workspace.c:meta_workspace_activate_with_focus(), where compositor-specific code is merged with the rest of the function (required to emit signal), removing #ifdefs.
2009-07-02 11:19:02 -04:00
CLEANFILES += $(MUTTER_STAMP_FILES)
Install enum types
2015-07-06 00:58:45 -04:00
meta/meta-enum-types.h: stamp-meta-enum-types.h Makefile
Emit signals when workspaces are added, removed or switched The patch adds GLib marshalling code to Mutter, since it's required for the "workspace-switched" signal. The definition of MetaMotionDirection enum is moved to common.h since it's now used in workspace.c. A little cleaning is done in workspace.c:meta_workspace_activate_with_focus(), where compositor-specific code is merged with the rest of the function (required to emit signal), removing #ifdefs.
2009-07-02 11:19:02 -04:00
@true
Install enum types
2015-07-06 00:58:45 -04:00
stamp-meta-enum-types.h: $(libmutterinclude_headers) meta-enum-types.h.in
Added --enable-silent-rules if automake-1.11 is available
2009-08-06 17:41:52 -04:00
$(AM_V_GEN) ( cd $(srcdir) && \
Emit signals when workspaces are added, removed or switched The patch adds GLib marshalling code to Mutter, since it's required for the "workspace-switched" signal. The definition of MetaMotionDirection enum is moved to common.h since it's now used in workspace.c. A little cleaning is done in workspace.c:meta_workspace_activate_with_focus(), where compositor-specific code is merged with the rest of the function (required to emit signal), removing #ifdefs.
2009-07-02 11:19:02 -04:00
$(GLIB_MKENUMS) \
Install enum types
2015-07-06 00:58:45 -04:00
--template meta-enum-types.h.in \
build: Fix enum types rules The list of files being parsed for enumerations include the header file we are building with the enumeration types. Additionally, we are concatenating multiple runs in the same temporary files; on failure, the temporary files are left around, which means we end up with broken headers and sources.
2017-07-16 06:39:03 -04:00
$(libmutterinclude_headers) ) > xgen-teth && \
Install enum types
2015-07-06 00:58:45 -04:00
(cmp -s xgen-teth meta/meta-enum-types.h || cp xgen-teth meta/meta-enum-types.h) && \
Emit signals when workspaces are added, removed or switched The patch adds GLib marshalling code to Mutter, since it's required for the "workspace-switched" signal. The definition of MetaMotionDirection enum is moved to common.h since it's now used in workspace.c. A little cleaning is done in workspace.c:meta_workspace_activate_with_focus(), where compositor-specific code is merged with the rest of the function (required to emit signal), removing #ifdefs.
2009-07-02 11:19:02 -04:00
rm -f xgen-teth && \
echo timestamp > $(@F)
Install enum types
2015-07-06 00:58:45 -04:00
meta-enum-types.c: stamp-meta-enum-types.h meta-enum-types.c.in
Added --enable-silent-rules if automake-1.11 is available
2009-08-06 17:41:52 -04:00
$(AM_V_GEN) ( cd $(srcdir) && \
Emit signals when workspaces are added, removed or switched The patch adds GLib marshalling code to Mutter, since it's required for the "workspace-switched" signal. The definition of MetaMotionDirection enum is moved to common.h since it's now used in workspace.c. A little cleaning is done in workspace.c:meta_workspace_activate_with_focus(), where compositor-specific code is merged with the rest of the function (required to emit signal), removing #ifdefs.
2009-07-02 11:19:02 -04:00
$(GLIB_MKENUMS) \
Install enum types
2015-07-06 00:58:45 -04:00
--template meta-enum-types.c.in \
build: Fix enum types rules The list of files being parsed for enumerations include the header file we are building with the enumeration types. Additionally, we are concatenating multiple runs in the same temporary files; on failure, the temporary files are left around, which means we end up with broken headers and sources.
2017-07-16 06:39:03 -04:00
$(libmutterinclude_headers) ) > xgen-tetc && \
Install enum types
2015-07-06 00:58:45 -04:00
cp xgen-tetc meta-enum-types.c && \
Emit signals when workspaces are added, removed or switched The patch adds GLib marshalling code to Mutter, since it's required for the "workspace-switched" signal. The definition of MetaMotionDirection enum is moved to common.h since it's now used in workspace.c. A little cleaning is done in workspace.c:meta_workspace_activate_with_focus(), where compositor-specific code is merged with the rest of the function (required to emit signal), removing #ifdefs.
2009-07-02 11:19:02 -04:00
rm -f xgen-tetc
configure: Adds --enable-wayland config option This adds a --enable-wayland configure option to enable building mutter as a hybrid X and Wayland compositor. By default the option is disabled. If enabled then HAVE_WAYLAND is defined for C code and as an automake conditional. This copies the xserver.xml wayland protocol into a protocol/ directory since wayland support will depend on this protocol for communicating with an xwayland X server. Copying the spec like this is consistent with Weston so we don't need a configure option to locate an external spec.
2012-01-05 07:19:58 -05:00
Remove "xrandr" from the name of the generated DBus files It's about generic display config, not XRandR specifically.
2014-03-31 23:33:01 -04:00
dbus_display_config_built_sources = meta-dbus-display-config.c meta-dbus-display-config.h
Introduce a new DBus interface for display configuration This new interface will be used by the control center and possibly the settings daemon to configure the screens. It is designed to resemble a simplified XRandR, while still exposing all the quirks of the hardware, so that the panel can limit the user choices appropriately. To do so, MetaMonitorMode needs to track CRTCs, outputs and modes, so the low level objects have been decoupled from the high-level MetaMonitorInfo, which is used by core and API and offers a simplified view of HW, that hides away the details of what is cloned and how. This is still not efficient as it should be, because on every HW change we drop all data structures and rebuild them from scratch (which is not expensive because there aren't many of them, but at least in the XRandR path it involves a few sync X calls) https://bugzilla.gnome.org/show_bug.cgi?id=705670
2013-07-19 08:39:28 -04:00
Remove "xrandr" from the name of the generated DBus files It's about generic display config, not XRandR specifically.
2014-03-31 23:33:01 -04:00
$(dbus_display_config_built_sources) : Makefile.am org.gnome.Mutter.DisplayConfig.xml
Merge tag 'xrandr_branch_point' into wayland-kms-base Conflicts: src/Makefile.am src/core/display.c src/core/screen-private.h src/core/screen.c
2013-08-27 04:07:39 -04:00
$(AM_V_GEN)gdbus-codegen \
Introduce a new DBus interface for display configuration This new interface will be used by the control center and possibly the settings daemon to configure the screens. It is designed to resemble a simplified XRandR, while still exposing all the quirks of the hardware, so that the panel can limit the user choices appropriately. To do so, MetaMonitorMode needs to track CRTCs, outputs and modes, so the low level objects have been decoupled from the high-level MetaMonitorInfo, which is used by core and API and offers a simplified view of HW, that hides away the details of what is cloned and how. This is still not efficient as it should be, because on every HW change we drop all data structures and rebuild them from scratch (which is not expensive because there aren't many of them, but at least in the XRandR path it involves a few sync X calls) https://bugzilla.gnome.org/show_bug.cgi?id=705670
2013-07-19 08:39:28 -04:00
--interface-prefix org.gnome.Mutter \
--c-namespace MetaDBus \
Remove "xrandr" from the name of the generated DBus files It's about generic display config, not XRandR specifically.
2014-03-31 23:33:01 -04:00
--generate-c-code meta-dbus-display-config \
Let gdbus-codegen generate autocleanup definitions This used to be the hardcoded behavior, but it broke some other users, so it was made conditional and default off.
2016-05-05 09:18:11 -04:00
--c-generate-autocleanup all \
Rename the DBus interface files
2014-03-31 23:31:42 -04:00
$(srcdir)/org.gnome.Mutter.DisplayConfig.xml
Merge tag 'xrandr_branch_point' into wayland-kms-base Conflicts: src/Makefile.am src/core/display.c src/core/screen-private.h src/core/screen.c
2013-08-27 04:07:39 -04:00
Rename the DBus interface files
2014-03-31 23:31:42 -04:00
$(dbus_idle_built_sources) : Makefile.am org.gnome.Mutter.IdleMonitor.xml
MetaIdleMonitor: add a DBus interface for the idle monitor To allow other clients (gnome-session, gnome-settings-daemon) to monitor user activity, introduce a DBus interface for the idle monitor inside mutter. https://bugzilla.gnome.org/show_bug.cgi?id=706005
2013-08-14 07:51:05 -04:00
$(AM_V_GEN)gdbus-codegen \
--interface-prefix org.gnome.Mutter \
--c-namespace MetaDBus \
--generate-c-code meta-dbus-idle-monitor \
--c-generate-object-manager \
Let gdbus-codegen generate autocleanup definitions This used to be the hardcoded behavior, but it broke some other users, so it was made conditional and default off.
2016-05-05 09:18:11 -04:00
--c-generate-autocleanup all \
Rename the DBus interface files
2014-03-31 23:31:42 -04:00
$(srcdir)/org.gnome.Mutter.IdleMonitor.xml
MetaIdleMonitor: add a DBus interface for the idle monitor To allow other clients (gnome-session, gnome-settings-daemon) to monitor user activity, introduce a DBus interface for the idle monitor inside mutter. https://bugzilla.gnome.org/show_bug.cgi?id=706005
2013-08-14 07:51:05 -04:00
Add remote desktop and screen cast functionality This commit adds basic screen casting and remote desktoping functionalty. This works by exposing two D-Bus API services: org.gnome.Mutter.ScreenCast and org.gnome.Mutter.RemoteDesktop. The remote desktop API is used to create remote desktop sessions. For each session, a D-Bus object is created, and an application can manage the session by sending messages to the session object. A remote desktop session the user to emit input events using the D-Bus methods on the session object. To get framebuffer content, the application should create an associated screen cast session. The screen cast API is used to create screen cast sessions. One can so far either create stand-alone screen cast sessions, or a screen cast session associated with a remote desktop session. A remote desktop associated screen cast session is managed by the remote desktop session. So far only remote desktop managed screen cast sessions are implemented. Each screen cast session may have one or more streams. A screen cast stream is a stream of buffers of some part of the compositor content. So far API exists for creating streams of monitors and windows, but only monitor streams are implemented. When a screen cast session is started, the one PipeWire stream is created for each screen cast stream created for the session. When this has happened, a PipeWireStreamAdded signal is emitted on the stream object, passing a unique identifier. The application may use this identifier to find the associated stream being advertised by the PipeWire daemon. The remote desktop and screen cast functionality must be explicitly be enabled at ./configure time by passing --enable-remote-desktop to ./configure. Doing this will build both screen cast and remote desktop support. To actually enable the screen casting and remote desktop, the user must enable the experimental feature. See org.gnome.mutter.experimental-features. https://bugzilla.gnome.org/show_bug.cgi?id=784199
2017-06-21 02:23:44 -04:00
if HAVE_REMOTE_DESKTOP
dbus_remote_desktop_built_sources = meta-dbus-remote-desktop.c meta-dbus-remote-desktop.h
$(dbus_remote_desktop_built_sources) : Makefile.am org.gnome.Mutter.RemoteDesktop.xml
$(AM_V_GEN)gdbus-codegen \
--interface-prefix org.gnome.Mutter \
--c-namespace MetaDBus \
--generate-c-code meta-dbus-remote-desktop \
$(srcdir)/org.gnome.Mutter.RemoteDesktop.xml
dbus_screen_cast_built_sources = meta-dbus-screen-cast.c meta-dbus-screen-cast.h
$(dbus_screen_cast_built_sources) : Makefile.am org.gnome.Mutter.ScreenCast.xml
$(AM_V_GEN)gdbus-codegen \
--interface-prefix org.gnome.Mutter \
--c-namespace MetaDBus \
--generate-c-code meta-dbus-screen-cast \
$(srcdir)/org.gnome.Mutter.ScreenCast.xml
endif
launcher: Replace mutter-launch with logind integration This uses David Herrmann's new logind sessions interface to retrieve fds for input devices, rather than using a custom setuid helper to do the management. This vastly simplifies the interface. This requires systemd v210, at least. https://bugzilla.gnome.org/show_bug.cgi?id=724604
2013-12-31 17:44:45 -05:00
dbus_login1_built_sources = meta-dbus-login1.c meta-dbus-login1.h
$(dbus_login1_built_sources) : Makefile.am org.freedesktop.login1.xml
$(AM_V_GEN)gdbus-codegen \
--interface-prefix org.freedesktop.login1 \
--c-namespace Login1 \
--generate-c-code meta-dbus-login1 \
Let gdbus-codegen generate autocleanup definitions This used to be the hardcoded behavior, but it broke some other users, so it was made conditional and default off.
2016-05-05 09:18:11 -04:00
--c-generate-autocleanup all \
launcher: Replace mutter-launch with logind integration This uses David Herrmann's new logind sessions interface to retrieve fds for input devices, rather than using a custom setuid helper to do the management. This vastly simplifies the interface. This requires systemd v210, at least. https://bugzilla.gnome.org/show_bug.cgi?id=724604
2013-12-31 17:44:45 -05:00
$(srcdir)/org.freedesktop.login1.xml
monitor-manager-kms: Add common modes Some output devices only advertise their preferred mode even though they're able to display others too. This means we can include some common modes in each output's supported list. This is particularly important for mirroring, since we can only mirror outputs which are using the same resolution. https://bugzilla.gnome.org/show_bug.cgi?id=744544
2015-02-14 15:03:38 -05:00
backends/native/meta-default-modes.h: backends/native/gen-default-modes.py Makefile.am
@if test -n "$(CVT)"; then \
if $(AM_V_P); then PS4= set -x; else echo " GEN $@"; fi; \
python $< > $@; \
fi
wayland: Use pointer gestures protocol from wayand-protocols Remove our own copy of the pointer gestures protocol, and us the one installed by wayland-protocols. This also means the new fixed unstable naming conventions are used for the new version of the protocol, which is reflected in the change. No functional changes were made, it is only a rename. https://bugzilla.gnome.org/show_bug.cgi?id=758633
2015-11-09 02:28:14 -05:00
.SECONDEXPANSION:
define protostability
$(shell echo $1 | sed 's/.*\(\<unstable\>\|\<stable\>\).*/\1/')
endef
define protoname
$(shell echo $1 | sed 's/\([a-z\-]\+\)-[a-z]\+-v[0-9]\+/\1/')
endef
%-protocol.c : $(WAYLAND_PROTOCOLS_DATADIR)/$$(call protostability,$$*)/$$(call protoname,$$*)/$$*.xml
src/Makefile.am: Pass protocol file to wayland-scanner as an argument Instead of piping the protocol file content to wayland-scanner, pass the file name as an argument. This enables a new enough wayland-scanner to print more meaningful error messages. https://bugzilla.gnome.org/show_bug.cgi?id=769936
2016-01-25 04:37:58 -05:00
$(AM_V_GEN)$(WAYLAND_SCANNER) code $< $@
wayland: Use pointer gestures protocol from wayand-protocols Remove our own copy of the pointer gestures protocol, and us the one installed by wayland-protocols. This also means the new fixed unstable naming conventions are used for the new version of the protocol, which is reflected in the change. No functional changes were made, it is only a rename. https://bugzilla.gnome.org/show_bug.cgi?id=758633
2015-11-09 02:28:14 -05:00
%-server-protocol.h : $(WAYLAND_PROTOCOLS_DATADIR)/$$(call protostability,$$*)/$$(call protoname,$$*)/$$*.xml
src/Makefile.am: Pass protocol file to wayland-scanner as an argument Instead of piping the protocol file content to wayland-scanner, pass the file name as an argument. This enables a new enough wayland-scanner to print more meaningful error messages. https://bugzilla.gnome.org/show_bug.cgi?id=769936
2016-01-25 04:37:58 -05:00
$(AM_V_GEN)$(WAYLAND_SCANNER) server-header $< $@
Don't generate sources in a subdirectory This fixes srcdir != builddir issues.
2014-03-18 22:06:20 -04:00
%-protocol.c : $(srcdir)/wayland/protocol/%.xml
src/Makefile.am: Pass protocol file to wayland-scanner as an argument Instead of piping the protocol file content to wayland-scanner, pass the file name as an argument. This enables a new enough wayland-scanner to print more meaningful error messages. https://bugzilla.gnome.org/show_bug.cgi?id=769936
2016-01-25 04:37:58 -05:00
$(AM_V_GEN)$(WAYLAND_SCANNER) code $< $@
Don't generate sources in a subdirectory This fixes srcdir != builddir issues.
2014-03-18 22:06:20 -04:00
%-server-protocol.h : $(srcdir)/wayland/protocol/%.xml
src/Makefile.am: Pass protocol file to wayland-scanner as an argument Instead of piping the protocol file content to wayland-scanner, pass the file name as an argument. This enables a new enough wayland-scanner to print more meaningful error messages. https://bugzilla.gnome.org/show_bug.cgi?id=769936
2016-01-25 04:37:58 -05:00
$(AM_V_GEN)$(WAYLAND_SCANNER) server-header $< $@
wayland: add keyboard shortcuts inhibitor protocol https://bugzilla.gnome.org/show_bug.cgi?id=783342
2017-03-21 06:47:16 -04:00
keyboard-shortcuts-inhibit-unstable-v1-protocol.c : $(WAYLAND_PROTOCOLS_DATADIR)/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
$(AM_V_GEN)$(WAYLAND_SCANNER) code < $< > $@
keyboard-shortcuts-inhibit-unstable-v1-server-protocol.h : $(WAYLAND_PROTOCOLS_DATADIR)/unstable/keyboard-shortcuts-inhibit/keyboard-shortcuts-inhibit-unstable-v1.xml
$(AM_V_GEN)$(WAYLAND_SCANNER) server-header < $< > $@
Reference in New Issue Copy Permalink