isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-27 10:30:47 -05:00
Code Issues Packages Projects Releases Wiki Activity
05353c1f7e
mutter/src/Makefile.am

475 lines
14 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:
Revert "wayland: make parallel installable with regular mutter" This reverts commit ea3d2b4759524345c89fe08ad0c159d7136dbdf1.
2014-04-09 18:12:50 -04:00
lib_LTLIBRARIES = libmutter.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 \
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 \
-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) \
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
mutter-enum-types.h \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
mutter-enum-types.c \
$(NULL)
Only build Wayland protocols when we have Wayland
2014-08-27 12:05:51 -04:00
if HAVE_WAYLAND
mutter_built_sources += \
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 \
xdg-shell-protocol.c \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
xdg-shell-server-protocol.h \
$(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 \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
wayland/protocol/xdg-shell.xml \
$(NULL)
Move Wayland protocols into src/wayland
2014-03-18 20:32:02 -04:00
Revert "wayland: make parallel installable with regular mutter" This reverts commit ea3d2b4759524345c89fe08ad0c159d7136dbdf1.
2014-04-09 18:12:50 -04:00
libmutter_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 \
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 \
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-private.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: 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 \
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-config.c \
backends/meta-monitor-config.h \
backends/meta-monitor-manager.c \
backends/meta-monitor-manager.h \
backends/meta-monitor-manager-dummy.c \
backends/meta-monitor-manager-dummy.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 \
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 \
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 \
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 \
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 \
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 \
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 \
Make MetaShadowFactory public The basic MetaShadowFactory type is moved to a public header, while the functions to fetch and paint shadows are kept private. The public object will be used for configuration of shadows by plugins. https://bugzilla.gnome.org/show_bug.cgi?id=592382
2010-11-11 10:21:36 -05:00
compositor/meta-shadow-factory-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-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 \
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/meta-window-shape.h \
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 \
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/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 \
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 \
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 \
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/iconcache.c \
x11/iconcache.h \
x11/async-getprop.c \
x11/async-getprop.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 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
if HAVE_WAYLAND
libmutter_la_SOURCES += \
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/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: 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/meta-wayland-keyboard.c \
wayland/meta-wayland-keyboard.h \
wayland/meta-wayland-pointer.c \
wayland/meta-wayland-pointer.h \
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: 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/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 \
window: Add a type for Wayland windows
2014-03-19 09:26:17 -04:00
wayland/window-wayland.c \
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
wayland/window-wayland.h \
$(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
libmutter_la_SOURCES += \
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 \
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 \
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/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
Makefile: Use $(NULL) trick This helps make the Makefile look nicer and prevent merge conflicts.
2014-11-04 22:06:55 -05:00
nodist_libmutter_la_SOURCES = $(mutter_built_sources)
Kill HAVE_WAYLAND
2014-02-17 21:28:41 -05:00
libmutter: Only export meta_* symbols in the library We also need ag_* symbols for testasyncgetprop.
2014-12-29 20:59:16 -05:00
libmutter_la_LDFLAGS = -no-undefined -export-symbols-regex "^(meta|ag)_.*"
Make the native backend build-optional
2014-05-29 12:11:26 -04:00
libmutter_la_LIBADD = $(MUTTER_LIBS) $(MUTTER_NATIVE_BACKEND_LIBS)
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 \
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 \
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 \
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 \
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 = \
meta/meta-version.h
libmutterinclude_base_headers = \
$(libmutterinclude_headers) \
$(libmutterinclude_built_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
# Excluded from scanning for introspection but installed
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
# atomnames.h: macros cause problems for scanning process
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_extra_headers = \
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/atomnames.h
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
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 = \
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) \
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_extra_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
mutter_LDADD = $(MUTTER_LIBS) libmutter.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
include $(INTROSPECTION_MAKEFILE)
Freeze api_version to 3.0 Back the API version down to 3.0; since we don't make any stability guarantees, there's no reason to have a merry-go-round of different directories and filenames that people have to keep up with.
2011-07-01 19:19:11 -04:00
# Since we don't make any guarantees about stability and we don't support
# parallel install, there's no real reason to change directories, filenames,
# etc. as we change the Mutter tarball version.
#api_version = $(MUTTER_MAJOR_VERSION).$(MUTTER_MINOR_VERSION)
api_version = 3.0
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)
gir_DATA = Meta-$(api_version).gir
typelibdir = $(pkglibdir)
typelib_DATA = Meta-$(api_version).typelib
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
INTROSPECTION_GIRS = Meta-$(api_version).gir
Revert "wayland: make parallel installable with regular mutter" This reverts commit ea3d2b4759524345c89fe08ad0c159d7136dbdf1.
2014-04-09 18:12:50 -04:00
Meta-$(api_version).gir: libmutter.la
Add the ability to add shader hooks to MetaBackgroundActor Using ClutterEffect is not pratical on MetaBackgroundActor, as the FBO redirection has a noticeable performance impact. Instead, allow adding GLSL code directly to the pipeline used to draw the background texture. At the same time, port MetaBackgroundActor to modern Cogl API. https://bugzilla.gnome.org/show_bug.cgi?id=669798
2012-08-29 19:45:17 -04:00
@META_GIR@_INCLUDES = GObject-2.0 GDesktopEnums-3.0 Gdk-3.0 Gtk-3.0 Clutter-1.0 xlib-2.0 xfixes-4.0 Cogl-1.0
Revert "wayland: make parallel installable with regular mutter" This reverts commit ea3d2b4759524345c89fe08ad0c159d7136dbdf1.
2014-04-09 18:12:50 -04:00
@META_GIR@_EXPORT_PACKAGES = libmutter
build: Fix some warnings and clean up a bit
2014-06-04 13:31:37 -04:00
@META_GIR@_CFLAGS = $(AM_CPPFLAGS)
Revert "wayland: make parallel installable with regular mutter" This reverts commit ea3d2b4759524345c89fe08ad0c159d7136dbdf1.
2014-04-09 18:12:50 -04:00
@META_GIR@_LIBS = libmutter.la
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
@META_GIR@_FILES = \
mutter-enum-types.h \
$(libmutterinclude_base_headers) \
Revert "wayland: make parallel installable with regular mutter" This reverts commit ea3d2b4759524345c89fe08ad0c159d7136dbdf1.
2014-04-09 18:12:50 -04:00
$(filter %.c,$(libmutter_la_SOURCES) $(nodist_libmutter_la_SOURCES))
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
@META_GIR@_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 = \
$(libmutterinclude_built_headers)
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
Revert "wayland: make parallel installable with regular mutter" This reverts commit ea3d2b4759524345c89fe08ad0c159d7136dbdf1.
2014-04-09 18:12:50 -04:00
pkgconfig_DATA = libmutter.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 \
mutter-enum-types.h.in \
mutter-enum-types.c.in \
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 \
$(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)
Use generic marshaller https://bugzilla.gnome.org/show_bug.cgi?id=662153
2011-10-18 18:06:14 -04:00
MUTTER_STAMP_FILES = stamp-mutter-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)
mutter-enum-types.h: stamp-mutter-enum-types.h Makefile
@true
Fix the dependency for mutter-enum-types.h mutter-enum-types.h is built from $(libmutterinclude_base_headers) not the non-existent $(mutter_source_h)
2009-08-31 18:12:29 -04:00
stamp-mutter-enum-types.h: $(libmutterinclude_base_headers) mutter-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) \
Fix out-of-tree build. This patch fixes an issue encountered when building mutter out-of-tree: * When generating mutter-enum-types.[ch], the glib-mkenums command is executed from $(srcdir), so it is wrong to prepend $(srcdir) to the template file. https://bugzilla.gnome.org/show_bug.cgi?id=624910
2010-08-13 09:06:35 -04:00
--template mutter-enum-types.h.in \
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
$(libmutterinclude_base_headers) ) >> xgen-teth && \
Added --enable-silent-rules if automake-1.11 is available
2009-08-06 17:41:52 -04:00
(cmp -s xgen-teth mutter-enum-types.h || cp xgen-teth mutter-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)
mutter-enum-types.c: stamp-mutter-enum-types.h mutter-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) \
Fix out-of-tree build. This patch fixes an issue encountered when building mutter out-of-tree: * When generating mutter-enum-types.[ch], the glib-mkenums command is executed from $(srcdir), so it is wrong to prepend $(srcdir) to the template file. https://bugzilla.gnome.org/show_bug.cgi?id=624910
2010-08-13 09:06:35 -04:00
--template mutter-enum-types.c.in \
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
$(libmutterinclude_base_headers) ) >> xgen-tetc && \
cp xgen-tetc mutter-enum-types.c && \
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 \
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 \
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
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 \
$(srcdir)/org.freedesktop.login1.xml
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
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
$(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
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
$(AM_V_GEN)$(WAYLAND_SCANNER) server-header < $< > $@
Reference in New Issue Copy Permalink