brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1617323dca
mutter/src/Makefile.am

390 lines
11 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:
Go with a single libmutter library https://bugzilla.gnome.org/show_bug.cgi?id=644565
2011-03-12 11:07:09 -05: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
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
INCLUDES= \
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 \
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) \
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) \
-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)\" \
-DHOST_ALIAS=\"@HOST_ALIAS@\" \
-DMUTTER_LOCALEDIR=\"$(prefix)/@DATADIRNAME@/locale\" \
-DMUTTER_PKGDATADIR=\"$(pkgdatadir)\" \
-DMUTTER_DATADIR=\"$(datadir)\" \
-DG_LOG_DOMAIN=\"mutter\" \
-DSN_API_NOT_YET_FROZEN=1 \
-DMUTTER_MAJOR_VERSION=$(MUTTER_MAJOR_VERSION) \
-DMUTTER_MINOR_VERSION=$(MUTTER_MINOR_VERSION) \
-DMUTTER_MICRO_VERSION=$(MUTTER_MICRO_VERSION) \
-DMUTTER_PLUGIN_API_VERSION=$(MUTTER_PLUGIN_API_VERSION) \
-DMUTTER_PKGLIBDIR=\"$(pkglibdir)\" \
-DMUTTER_PLUGIN_DIR=\"@MUTTER_PLUGIN_DIR@\" \
-DGETTEXT_PACKAGE=\"$(GETTEXT_PACKAGE)\"
...
2001-06-02 00:14:18 -04:00
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
if HAVE_WAYLAND
INCLUDES += \
-I$(srcdir)/wayland \
build: Fix srcdir != builddir Need to ensure the wayland/ directory exists in $(builddir), and find the headers there too.
2013-08-17 17:50:07 -04:00
-I$(builddir)/wayland \
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
-DXWAYLAND_PATH='"@XWAYLAND_PATH@"'
endif
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 = \
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) \
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
mutter-enum-types.c
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
if HAVE_WAYLAND
mutter_built_sources += \
wayland/xserver-protocol.c \
wayland/xserver-server-protocol.h \
wayland/xserver-client-protocol.h
endif
Go with a single libmutter library https://bugzilla.gnome.org/show_bug.cgi?id=644565
2011-03-12 11:07:09 -05:00
libmutter_la_SOURCES = \
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/async-getprop.c \
core/async-getprop.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
core/barrier.c \
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 \
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 \
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 \
compositor/meta-background-group-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 \
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 \
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 \
Add an "Above_Tab" pseudo-keysym We want switching between the windows of an application to be an easily accessible operation. The convenient and memorable keybinding is the key above the tab key - but the keysym for that key isn't consistent across different keyboard layouts. Add code that figures out the key from the XKB geometry and a magic keysym name "Above_Tab" that refers to this key and switch the default binding for cycle_group to <Alt>Above_Tab. (This will have no effect for the normal case of getting the key binding from GConf until this patch is applied to Metacity as well.) https://bugzilla.gnome.org/show_bug.cgi?id=635569
2010-11-22 18:21:47 -05:00
core/above-tab-keycode.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/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
ui/draw-workspace.c \
draw-workspace.h is in ui, not core. 2008-02-02 Thomas Thurman <tthurman@gnome.org> * src/Makefile.am: draw-workspace.h is in ui, not core. svn path=/trunk/; revision=3535
2008-02-02 16:35:23 -05:00
ui/draw-workspace.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 \
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 \
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/gradient.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/gradient.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/group-private.h \
core/group-props.c \
core/group-props.h \
core/group.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/group.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/iconcache.c \
core/iconcache.h \
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 \
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
core/meta-cursor-tracker.c \
core/meta-cursor-tracker-private.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
core/meta-idle-monitor.c \
core/meta-idle-monitor-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
core/mutter-Xatomtype.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/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 \
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/session.c \
core/session.h \
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 \
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-props.c \
core/window-props.h \
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 \
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/xprops.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/xprops.h \
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/menu.c \
ui/menu.h \
ui/metaaccellabel.c \
ui/metaaccellabel.h \
ui/resizepopup.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
ui/resizepopup.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/tabpopup.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
ui/tabpopup.h \
Implement side-by-side tiling When dragging a window over a screen edge and dropping it there, maximize it vertically and scale it horizontally to cover the corresponding half of the current monitor. Whenever a "hot area" which triggers this behavior is entered, an indication of window's target size is displayed after a short delay to avoid distraction when moving a window between monitors. https://bugzilla.gnome.org/show_bug.cgi?id=606260
2010-06-24 14:41:28 -04:00
ui/tile-preview.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
ui/tile-preview.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/theme-parser.c \
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 \
Fixes to make distcheck work again. 2008-10-22 Thomas Thurman <tthurman@gnome.org> Fixes to make distcheck work again. * src/Makefile.am: include *-binding.h, and make the schema building work when builddir != srcdir * po/POTFILES.in (src/core/keybindings.): include *-binding.h svn path=/trunk/; revision=3985
2008-10-22 09:08:44 -04:00
ui/ui.c \
Go with a single libmutter library https://bugzilla.gnome.org/show_bug.cgi?id=644565
2011-03-12 11:07:09 -05:00
$(mutter_built_sources)
move in here so util.c doesn't require display.[hc] 2002-01-27 Havoc Pennington <hp@pobox.com> * src/display.c (meta_set_syncing): move in here so util.c doesn't require display.[hc] * src/theme.h, src/theme.c: implement coordinate expression parser, write MetaShapeSpec declaration * src/util.c (meta_exit): move in here so we can link to util.c with a different main() * src/theme.h: rename the MetaWindow* enums to MetaFrame*
2002-01-27 21:09:12 -05:00
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
if HAVE_WAYLAND
libmutter_la_SOURCES += \
wayland/meta-wayland.c \
wayland/meta-wayland-private.h \
wayland/meta-xwayland-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 \
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/meta-wayland-stage.h \
wayland/meta-wayland-stage.c
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
endif
Go with a single libmutter library https://bugzilla.gnome.org/show_bug.cgi?id=644565
2011-03-12 11:07:09 -05:00
libmutter_la_LDFLAGS = -no-undefined
libmutter_la_LIBADD = $(MUTTER_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
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_base_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 \
meta/gradient.h \
meta/group.h \
meta/keybindings.h \
meta/main.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 \
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 \
meta/meta-background.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 \
meta/workspace.h
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
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
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
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 = \
$(libmutterinclude_base_headers) \
$(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
Reintroduce mutter binary I accidentally deleted one too many things.
2013-08-13 10:16:01 -04:00
bin_PROGRAMS=mutter
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
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_SOURCES = core/mutter.c
Go with a single libmutter library https://bugzilla.gnome.org/show_bug.cgi?id=644565
2011-03-12 11:07:09 -05:00
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
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
Go with a single libmutter library https://bugzilla.gnome.org/show_bug.cgi?id=644565
2011-03-12 11:07:09 -05: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
Fix introspection gir metadata The EXPORT_PACKAGES variable to the GIR makefile should be the packages needed to use this gir. It's also unnecessary to set PACKAGES (which is just used for CFLAGS at scan-time) since CFLAGS is already pulls in all necessary CFLAGS. https://bugzilla.gnome.org/show_bug.cgi?id=671092
2012-02-29 17:52:27 -05:00
@META_GIR@_EXPORT_PACKAGES = libmutter
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@_CFLAGS = $(INCLUDES)
Go with a single libmutter library https://bugzilla.gnome.org/show_bug.cgi?id=644565
2011-03-12 11:07:09 -05: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) \
Go with a single libmutter library https://bugzilla.gnome.org/show_bug.cgi?id=644565
2011-03-12 11:07:09 -05:00
$(filter %.c,$(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
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
testboxes_SOURCES = core/testboxes.c
testgradient_SOURCES = ui/testgradient.c
testasyncgetprop_SOURCES = core/testasyncgetprop.c
change to use spiffy gradient code. 2002-01-06 Havoc Pennington <hp@pobox.com> * src/theme.c (meta_theme_get_gradient): change to use spiffy gradient code. * src/gradient.c: copy lovely gradient code from WindowMaker, as usual Dan and Alfredo have very nice code
2002-01-06 12:52:21 -05: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
noinst_PROGRAMS=testboxes testgradient testasyncgetprop
change to use spiffy gradient code. 2002-01-06 Havoc Pennington <hp@pobox.com> * src/theme.c (meta_theme_get_gradient): change to use spiffy gradient code. * src/gradient.c: copy lovely gradient code from WindowMaker, as usual Dan and Alfredo have very nice code
2002-01-06 12:52:21 -05:00
Go with a single libmutter library https://bugzilla.gnome.org/show_bug.cgi?id=644565
2011-03-12 11:07:09 -05:00
testboxes_LDADD = $(MUTTER_LIBS) libmutter.la
testgradient_LDADD = $(MUTTER_LIBS) libmutter.la
testasyncgetprop_LDADD = $(MUTTER_LIBS) libmutter.la
change to use spiffy gradient code. 2002-01-06 Havoc Pennington <hp@pobox.com> * src/theme.c (meta_theme_get_gradient): change to use spiffy gradient code. * src/gradient.c: copy lovely gradient code from WindowMaker, as usual Dan and Alfredo have very nice code
2002-01-06 12:52:21 -05:00
Install desktop files in both .../share/applications and 2008-09-12 Vincent Untz <vuntz@gnome.org> Install desktop files in both .../share/applications and .../share/gnome/wm-properties. Copied in from the 2.23.x branch. Closes #549479. * src/metacity-wm.desktop.in: new file * src/.cvsignore: include the above * src/Makefile.am: install the above svn path=/trunk/; revision=3886
2008-09-12 00:05:17 -04:00
@INTLTOOL_DESKTOP_RULE@
Desktop file moved, according to policy change. Closes #549479. 2008-09-02 Thomas Thurman <tthurman@gnome.org> Desktop file moved, according to policy change. Closes #549479. * src/metacity.desktop.in: Don't display the desktop file * src/Makefile.am: Desktop file goes in apps directory svn path=/trunk/; revision=3846
2008-09-02 14:49:11 -04:00
desktopfilesdir=$(datadir)/applications
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
desktopfiles_in_files=mutter.desktop.in
don't install .desktop file for properties dialog if we aren't 2003-01-10 Havoc Pennington <hp@redhat.com> * src/Makefile.am (desktopfiles_DATA): don't install .desktop file for properties dialog if we aren't building/installing the properties dialog.
2003-01-10 15:43:47 -05:00
desktopfiles_files=$(desktopfiles_in_files:.desktop.in=.desktop)
desktopfiles_DATA = $(desktopfiles_files)
make Metacity install its desktop files in the default session directory 2008-03-29 Lucas Rocha <lucasr.at.mundo@gmail.com> * src/metacity.desktop.in, src/Makefile.am: make Metacity install its desktop files in the default session directory as required by the new gnome-session. (Closes #525051.) svn path=/trunk/; revision=3669
2008-03-29 20:01:18 -04:00
Install desktop files in both .../share/applications and 2008-09-12 Vincent Untz <vuntz@gnome.org> Install desktop files in both .../share/applications and .../share/gnome/wm-properties. Copied in from the 2.23.x branch. Closes #549479. * src/metacity-wm.desktop.in: new file * src/.cvsignore: include the above * src/Makefile.am: install the above svn path=/trunk/; revision=3886
2008-09-12 00:05:17 -04:00
wmpropertiesdir=$(datadir)/gnome/wm-properties
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
wmproperties_in_files=mutter-wm.desktop.in
Install desktop files in both .../share/applications and 2008-09-12 Vincent Untz <vuntz@gnome.org> Install desktop files in both .../share/applications and .../share/gnome/wm-properties. Copied in from the 2.23.x branch. Closes #549479. * src/metacity-wm.desktop.in: new file * src/.cvsignore: include the above * src/Makefile.am: install the above svn path=/trunk/; revision=3886
2008-09-12 00:05:17 -04:00
wmproperties_files=$(wmproperties_in_files:.desktop.in=.desktop)
wmproperties_DATA = $(wmproperties_files)
make test apps noinst 2001-09-04 Havoc Pennington <hp@pobox.com> * src/wm-tester/Makefile.am (noinst_PROGRAMS): make test apps noinst * src/metacity.desktop: for the capplet * src/Makefile.am: add .desktop file
2001-09-04 23:57:45 -04:00
keybindings: Add toggle-tile-left/right bindings Having keybindings for side-by-side tiling has been requested for a long time, so add this support now. https://bugzilla.gnome.org/show_bug.cgi?id=648700
2011-11-15 11:29:56 -05:00
xmldir = @GNOME_KEYBINDINGS_KEYSDIR@
xml_in_files = \
keybindings: Import keybinding files from Metacity Fallback mode is going away, so we should stop depending on Metacity for keybinding files for common bindings. https://bugzilla.gnome.org/show_bug.cgi?id=687672
2012-11-05 08:55:15 -05:00
50-mutter-navigation.xml.in \
50-mutter-system.xml.in \
keybindings: Add toggle-tile-left/right bindings Having keybindings for side-by-side tiling has been requested for a long time, so add this support now. https://bugzilla.gnome.org/show_bug.cgi?id=648700
2011-11-15 11:29:56 -05:00
50-mutter-windows.xml.in
xml_DATA = $(xml_in_files:.xml.in=.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
dbus_idle_built_sources = meta-dbus-idle-monitor.c meta-dbus-idle-monitor.h
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 12:14:15 -04:00
gsettings_SCHEMAS = org.gnome.mutter.gschema.xml
Add new control-center key bindings definitions (Closes: #420145) 2007-04-05 Bastien Nocera <hadess@hadess.net> * src/50-metacity-desktop-key.xml.in: * src/50-metacity-key.xml.in: * src/Makefile.am: Add new control-center key bindings definitions (Closes: #420145) 2007-04-05 Bastien Nocera <hadess@hadess.net> * POTFILES.in: add the XML keys definitions to the list svn path=/trunk/; revision=3170
2007-04-05 05:22:19 -04:00
@INTLTOOL_XML_NOMERGE_RULE@
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 12:14:15 -04:00
@GSETTINGS_RULES@
Add new control-center key bindings definitions (Closes: #420145) 2007-04-05 Bastien Nocera <hadess@hadess.net> * src/50-metacity-desktop-key.xml.in: * src/50-metacity-key.xml.in: * src/Makefile.am: Add new control-center key bindings definitions (Closes: #420145) 2007-04-05 Bastien Nocera <hadess@hadess.net> * POTFILES.in: add the XML keys definitions to the list svn path=/trunk/; revision=3170
2007-04-05 05:22:19 -04:00
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 12:14:15 -04:00
convertdir = $(datadir)/GConf/gsettings
Fix installation of mutter-schemas.convert
2011-11-11 15:39:54 -05:00
convert_DATA = mutter-schemas.convert
move SM init a bit later in the process, and init prefs 2001-12-09 Havoc Pennington <hp@pobox.com> * src/main.c (main): move SM init a bit later in the process, and init prefs * src/session.c: fix no SM case (though I hardly know why I'm bothering) * src/main.c (main): call bindtextdomain * src/util.h (_): actually call gettext * configure.in: put in AM_GLIB_GNU_GETTEXT and gconf stuff * src/prefs.c: Preferences - this marks the beginning of our doom. None of them are actually implemented yet, but we monitor some stuff from gconf.
2001-12-09 17:41:12 -05:00
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.desktop \
mutter-wm.desktop \
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 12:14:15 -04:00
org.gnome.mutter.gschema.xml \
keybindings: Add toggle-tile-left/right bindings Having keybindings for side-by-side tiling has been requested for a long time, so add this support now. https://bugzilla.gnome.org/show_bug.cgi?id=648700
2011-11-15 11:29:56 -05:00
$(xml_DATA) \
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
$(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
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
Go with a single libmutter library https://bugzilla.gnome.org/show_bug.cgi?id=644565
2011-03-12 11:07:09 -05:00
pkgconfig_DATA = libmutter.pc mutter-plugins.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
don't install .desktop file for properties dialog if we aren't 2003-01-10 Havoc Pennington <hp@redhat.com> * src/Makefile.am (desktopfiles_DATA): don't install .desktop file for properties dialog if we aren't building/installing the properties dialog.
2003-01-10 15:43:47 -05:00
EXTRA_DIST=$(desktopfiles_files) \
Changes necessary to build plugins out of tree: metacity-plugins.pc.in installation necessary header files fixed misplaced inclusion of config.h
2008-10-28 06:45:45 -04:00
$(wmproperties_files) \
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
$(IMAGES) \
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
$(desktopfiles_in_files) \
Install desktop files in both .../share/applications and 2008-09-12 Vincent Untz <vuntz@gnome.org> Install desktop files in both .../share/applications and .../share/gnome/wm-properties. Copied in from the 2.23.x branch. Closes #549479. * src/metacity-wm.desktop.in: new file * src/.cvsignore: include the above * src/Makefile.am: install the above svn path=/trunk/; revision=3886
2008-09-12 00:05:17 -04:00
$(wmproperties_in_files) \
keybindings: Add toggle-tile-left/right bindings Having keybindings for side-by-side tiling has been requested for a long time, so add this support now. https://bugzilla.gnome.org/show_bug.cgi?id=648700
2011-11-15 11:29:56 -05:00
$(xml_in_files) \
Port preferences to GSettings Move preferences to GSettings, using mainly shared schemas from gsettings-desktop-schemas. Unlike GConf, GSettings support is not optional, as Gio is already a hard dependency of GTK+. https://bugzilla.gnome.org/show_bug.cgi?id=635378
2011-06-24 12:14:15 -04:00
org.gnome.mutter.gschema.xml.in \
Fix installation of mutter-schemas.convert
2011-11-11 15:39:54 -05:00
mutter-schemas.convert \
Go with a single libmutter library https://bugzilla.gnome.org/show_bug.cgi?id=644565
2011-03-12 11:07:09 -05:00
libmutter.pc.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
mutter-plugins.pc.in \
Add bits missing from last commit Try to reconstruct the marshal list and enum type templates and add templates to extra dist list.
2009-07-04 11:37:26 -04:00
mutter-enum-types.h.in \
Use generic marshaller https://bugzilla.gnome.org/show_bug.cgi?id=662153
2011-10-18 18:06:14 -04:00
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
menu: Remove support for icon items from the window menu We don't show these by default, and it uses deprecated API. This also removes our only use of the stock icons, so remove those as well. https://bugzilla.gnome.org/show_bug.cgi?id=704437
2013-07-17 23:10:18 -04:00
BUILT_SOURCES = $(mutter_built_sources)
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
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
$(dbus_idle_built_sources) : Makefile.am idle-monitor.xml
$(AM_V_GEN)gdbus-codegen \
--interface-prefix org.gnome.Mutter \
--c-namespace MetaDBus \
--generate-c-code meta-dbus-idle-monitor \
--c-generate-object-manager \
$(srcdir)/idle-monitor.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
if HAVE_WAYLAND
wayland/%-protocol.c : $(top_builddir)/protocol/%.xml
build: Fix srcdir != builddir Need to ensure the wayland/ directory exists in $(builddir), and find the headers there too.
2013-08-17 17:50:07 -04:00
mkdir -p wayland
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 < $< > $@
wayland/%-server-protocol.h : $(top_builddir)/protocol/%.xml
build: Fix srcdir != builddir Need to ensure the wayland/ directory exists in $(builddir), and find the headers there too.
2013-08-17 17:50:07 -04:00
mkdir -p wayland
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 < $< > $@
wayland/%-client-protocol.h : $(top_builddir)/protocol/%.xml
build: Fix srcdir != builddir Need to ensure the wayland/ directory exists in $(builddir), and find the headers there too.
2013-08-17 17:50:07 -04:00
mkdir -p wayland
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) client-header < $< > $@
endif
Reference in New Issue Copy Permalink