Go to file
Robert Bragg 2e61318914 framebuffer: make format internal
This removes cogl_framebuffer_get_color_format() since the actual
internal format isn't strictly controlled by us. CoglFramebuffer::format
has been renamed to ::internal_format to make it clearer that it only
really represents the premultiplication status.

The plan is to make most of the work involved in creating a texture
happen lazily when allocating so this patch also changes
_cogl_framebuffer_init() to not take a format argument anymore since we
won't know the format of offscreen framebuffers until the framebuffer is
allocated, after the corresponding texture has been allocated. In the
case of offscreen framebuffers we now update the framebuffer
internal_format during allocation.

Reviewed-by: Neil Roberts <neil@linux.intel.com>

(cherry picked from commit 8cc9e1c8bd2fac8b2a95087249c23c952d5e379f)

Note: Since we can't break API compatibility on the 1.x branch this
actually keeps the cogl_framebuffer_get_color_format() api but moves it
into a new deprecated/cogl-framebuffer-deprecated.c file and it now
returns the newly name ::internal_format.
2014-01-09 15:29:30 +00:00
build Build a .xz file on release instead of a .bzip2 file 2013-09-23 18:22:32 +01:00
cogl framebuffer: make format internal 2014-01-09 15:29:30 +00:00
cogl-gles2 build: update to build with automake 1.13 2013-01-22 18:00:05 +00:00
cogl-gst cogl-gst: video-sink: fix YV12/I420 support 2014-01-01 17:56:46 +00:00
cogl-pango Use COGL_FLAGS_* for the context's private feature flags 2013-11-28 18:12:22 +00:00
cogl-path cogl-path: Export cogl_clip_push_from_path 2013-12-11 22:08:50 +00:00
deps build: fix make dist 2013-01-22 17:48:03 +00:00
doc framebuffer: make format internal 2014-01-09 15:29:30 +00:00
examples Make cogl-sdl.h a top-level header 2013-12-11 18:49:19 +00:00
po [l10n] Updated Italian translation. 2013-04-28 19:24:20 +02:00
test-fixtures Declare interface types as void and remove cast macros 2013-11-27 19:33:44 +00:00
tests Fix calculating the bounds when clipping from a primitive 2013-12-03 15:28:35 +00:00
.gitignore Update .gitignore 2013-11-29 14:04:39 +00:00
.vimrc misc: Add a .vimrc file 2011-05-17 15:24:54 +01:00
autogen.sh Add support for automake 1.14 2013-07-03 18:11:53 +01:00
ChangeLog dist: Don't use elaborate script to gen Changelogs 2011-07-20 16:58:46 +01:00
cogl.doap Adds an initial cogl.doap file 2011-05-06 12:12:13 +01:00
config-custom.h configure: Force #undef of 'near' and 'far' on Windows 2011-06-14 12:14:02 +01:00
config.h.win32.in Update config.h.win32.in 2013-03-15 00:26:35 +08:00
configure.ac Build and install cogl-path as a shared library 2013-12-11 18:49:19 +00:00
COPYING Update the COPYING file 2011-09-05 19:02:05 +01:00
Makefile.am Build and install cogl-path as a shared library 2013-12-11 18:49:19 +00:00
NEWS Updates NEWS for the 1.16.0 release 2013-09-23 15:24:19 +01:00
README.in README: misc updates 2013-07-09 22:54:02 +01:00

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.