Read-only mirror of https://gitlab.gnome.org/GNOME/mutter
b3cc4d26d9
Instead of queuing the frame sync event immediately after a swap, the Wayland winsys now installs a frame callback and queues the event when Wayland reports that the frame is complete. It also reports the COGL_FRAME_EVENT_COMPLETE event at the same time because there is no more information we can give. This patch is a bit of a divergence from how the events are handled in the GLX winsys. Instead of installing its own idle function, the _cogl_onscreen_queue_event() function has now been made non-static so that it can be used by the Wayland winsys. The frame callback now just queues an event using that. The pending_frame_infos queue on the CoglOnscreen isn't used and instead the CoglFrameInfo is immediately popped off the queue so that it can be stored as part of the closure data when the frame callback is set up. That way it would use the right frame info even if somehow the Wayland callbacks were invoked in the wrong order and the code is a bit simpler. Reviewed-by: Robert Bragg <robert@linux.intel.com> (cherry picked from commit f7ea370a0d5013c9f0263f37c7f892adc8a2f087) |
||
---|---|---|
build | ||
cogl | ||
cogl-gles2 | ||
cogl-gst | ||
cogl-pango | ||
deps | ||
doc | ||
examples | ||
po | ||
test-fixtures | ||
tests | ||
.gitignore | ||
.vimrc | ||
autogen.sh | ||
ChangeLog | ||
cogl.doap | ||
config-custom.h | ||
config.h.win32.in | ||
configure.ac | ||
COPYING | ||
Makefile.am | ||
NEWS | ||
README.in |
README for Cogl @COGL_1_VERSION@ =============================================================================== Note: This file is delimited with -- markers so it is possible to split sections out for other purposes, such as for release notes. -- DESCRIPTION ------------------------------------------------------------------------------- Cogl is a small open source library for using 3D graphics hardware for rendering. The API departs from the flat state machine style of OpenGL and is designed to make it easy to write orthogonal components that can render without stepping on each others toes. As well as aiming for a nice API, we think having a single library as opposed to an API specification like OpenGL has a few advantages too; like being able to paper over the inconsistencies/bugs of different OpenGL implementations in a centralized place, not to mention the myriad of OpenGL extensions. It also means we are in a better position to provide utility APIs that help software developers since they only need to be implemented once and there is no risk of inconsistency between implementations. Having other backends, besides OpenGL, such as drm, Gallium or D3D are options we are interested in for the future. -- REQUIREMENTS ------------------------------------------------------------------------------- Cogl currently only requires: • OpenGL ≥ 1.3 (or 1.2 + multitexturing), or OpenGL ES 2.0 (or 1.1) • GLX, AGL, WGL or an EGL implementation Cogl also has optional dependencies: • GLib ≥ @GLIB_REQ_VERSION@ - for gtype integration • GDK-Pixbuf ≥ @GDK_PIXBUF_REQ_VERSION@ - for image loading • Cairo ≥ @CAIRO_REQ_VERSION@ - for debugging texture atlasing (debug builds only) The optional Cogl Pango library requires: • Cairo ≥ @CAIRO_REQ_VERSION@ • PangoCairo ≥ @PANGOCAIRO_REQ_VERSION@ The optional Cogl GStreamer library requires: • GStreamer 1.0 On X11, Cogl depends on the following extensions • XComposite ≥ @XCOMPOSITE_REQ_VERSION@ • XDamage • XExt • XFixes ≥ @XFIXES_REQ_VERSION@ For the Wayland backend, Cogl requires: • Wayland ≥ @WAYLAND_REQ_VERSION@ When running with OpenGL, Cogl requires at least version 1.3 or 1.2 with the multitexturing extension. However to build Cogl you will need the latest GL headers which can be obtained from: http://www.khronos.org If you are building the API reference you will also need: • GTK-Doc ≥ @GTK_DOC_REQ_VERSION@ If you are building the additional documentation you will also need: • xsltproc • jw (optional, for generating PDFs) If you are building the Introspection data you will also need: • GObject-Introspection ≥ @GI_REQ_VERSION@ GObject-Introspection is available from: git://git.gnome.org/gobject-introspection If you want support for profiling Cogl you will also need: • UProf ≥ @UPROF_REQ_VERSION@ UProf is available from: git://github.com/rib/UProf.git -- DOCUMENTATION ------------------------------------------------------------------------------- The 1.x stable API is documented here: http://developer.gnome.org/cogl/stable/ The 1.x development API is documented here: http://developer.gnome.org/cogl/1.@COGL_1_MINOR_VERSION@ The experimental 2.0 API is documented here: http://cogl3d.org/cogl2-reference/ -- LICENSE ------------------------------------------------------------------------------- Most of Cogl is licensed under the terms of the GNU Lesser General Public License, version 2.1 or (at your option) later. Some files are licensed under more permissive licenses MIT or BSD style licenses though so please see individual files for details. -- BUILDING AND INSTALLATION ------------------------------------------------------------------------------- Please refer to the INSTALL document. -- BUGS ------------------------------------------------------------------------------- Please report bugs here: http://bugzilla.gnome.org/enter_bug.cgi?product=cogl You will need a Bugzilla account. Please include the following in bug reports: • what system you're running Cogl on; • which version of Cogl you are using; • which version of GLib and OpenGL (or OpenGL ES) you are using; • which video card and which drivers you are using, including output of glxinfo and xdpyinfo (if applicable); • how to reproduce the bug. If you cannot reproduce the bug with one of the tests that come with Cogl's source code, it can help a lot to include a small test case displaying the bad behaviour. If the bug exposes a crash, the exact text printed out and a stack trace obtained using gdb are greatly appreciated. -- CONTRIBUTING ------------------------------------------------------------------------------- The CODING_STYLE file describes the coding style we use throughout Cogl, please try your best to conform to this style because the consistency really helps keep the code maintainable. We can accept contributions in several ways: • Either as patches attached to bugs on bugzilla - For this you may be interested in using git-bz. See http://git.fishsoup.net/man/git-bz.html for details • You can email us patches - For this we recommend using git-send-email • You can create a remote branch and ask us to pull from that for more substantial changes. - For this we recommend using github. Ideally standalone patches should be created using git format-patch since that makes it easiest to import the patch with a commit message into a git repository.