[Bug 688407] [waylandsink] 0.10.x waylandsink is not Wayland 1.0 protocol compatible

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Fri Nov 30 10:36:31 PST 2012


https://bugzilla.gnome.org/show_bug.cgi?id=688407
  GStreamer | gst-plugins-bad | 0.10.x

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.10.24

--- Comment #4 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2012-11-30 18:36:28 UTC ---
Thanks, pushed:


commit 72aa2625526f04cb5c191c0c2525bde4e7f9c8e6
Author: Tim-Philipp Müller <tim.muller at collabora.co.uk>
Date:   Fri Nov 30 18:32:36 2012 +0000

    configure: fix wayland check

    Get rid of cruft we don't need, and make work properly
    when wayland is installed in a non-standard prefix, by
    not overriding WAYLAND_CFLAGS and WAYLAND_LIBS for no
    reason.

    https://bugzilla.gnome.org/show_bug.cgi?id=688407

commit 27bd971b743067bce607809e0a5cb26eab5c69a9
Author: Rob Bradford <rob at linux.intel.com>
Date:   Fri Nov 30 12:02:33 2012 +0000

    waylandsink: Port to 1.0 protocol

    - The globals are now notified through a wl_registry object
    - Since surface state is double buffered in the compositor it is now
necessary
    to call wl_surface_commit to atomically update surface state
    - Implement the ping/pong protocol which the compositor uses to check the
    client is still alive
    - SHM buffers are now allocated through a pool
    - It is necessary to make the surface top level before the contents will be
    presented by the compositor
    - Adopt the new event handling - through wl_display_dispatch
    - Update the configure check to look for Wayland 1.0

    https://bugzilla.gnome.org/show_bug.cgi?id=688407

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list