| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
We tried to resolve non-introspected types; lets skip those. We didn't
have a vfunc scope on a for-each loop; declared it synchronous.
https://bugzilla.gnome.org/show_bug.cgi?id=769800
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=769054
|
|
|
|
|
|
|
| |
On i686, the GLsizeiptr typedef in cogl-gles2.h conflicts with the
system GL headers, so make sure we don't include both.
https://bugzilla.gnome.org/show_bug.cgi?id=769014
|
| |
|
|
|
|
|
|
|
| |
By only showing the g-ir-scanner void typedefs it will make it print
warnings. Lets please it by showing the actual typedef.
https://bugzilla.gnome.org/show_bug.cgi?id=768977
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=768977
|
|
|
|
|
|
|
|
|
|
|
| |
Mutter (and libmutter users) are the only users of this version of
cogl, and will more or less only use the cogl-1.0, cogl-2.0 and cogl
experimental API variants, and having the possibility of having
different API versions of the same API depending on what file includes
it is error prone and confusing. Lets just remove the possibility of
having different versions of the same API.
https://bugzilla.gnome.org/show_bug.cgi?id=768977
|
|
|
|
|
|
|
|
| |
We bypass our build configuration to fetch API from a version which
isn't the one we actually use. Stop bypassing and just admit that the
1.0 API is still there, but still deprecated.
https://bugzilla.gnome.org/show_bug.cgi?id=768977
|
|
|
|
|
|
| |
None were used; no reason to keep them.
https://bugzilla.gnome.org/show_bug.cgi?id=768977
|
|
|
|
|
|
| |
We were not using it anywhere; lets get rid of it.
https://bugzilla.gnome.org/show_bug.cgi?id=768977
|
|
|
|
|
|
| |
We were no longer using anything from it; lets remove it.
https://bugzilla.gnome.org/show_bug.cgi?id=768977
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=768977
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CoglFrameInfo is a frame info container associated with a single
onscreen framebuffer. The clutter stage will eventually support drawing
a stage frame with multiple onscreen framebuffers, thus needs its own
frame info container.
This patch introduces a new stage signal 'presented' and a accompaning
ClutterFrameInfo and adapts the stage windows and past onscreen frame
callbacks users to use the signal and new info container.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
|
|
|
|
|
| |
Move the KMS interaction from cogl into mutter, where most of the other
KMS interaction already takes place. This also removes dead code which
were only excercised when non-mutter callers used the cogl KMS backend.
The cogl KMS API was updated to pass via MetaRendererNative instead of
via the different cogl objects.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
|
| |
If we want to put a cogl winsys backend in mutter, that backend need to
have access to the internal workings of cogl.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
| |
We require glib and don't support building on win32 any more.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
|
| |
The cogl/clutter merge made the .gitignore files in the respective
directories incorrect, due to the using absolute paths.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
|
|
| |
In cogl use cogl-config.h and in clutter use clutter-build-config.h. We
can't use clutter-config.h in clutter because its already used and
installed.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
| |
This is so we can use as base in mutter's future winsys backends.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
|
|
|
| |
If you include a file that might define __INSIDE_COGL_H__, don't
undefine it if it wasn't defined in that file. This makes it possible
to include for example cogl-gles2.h from some other file which defines
__INSIDE_COGL_H__.
https://bugzilla.gnome.org/show_bug.cgi?id=768976
|
|
|
|
|
|
|
|
|
|
| |
When using a context with robustness, glGetError() may return
GL_CONTEXT_LOST at any time and this error doesn't get cleared until
the application calls glGetGraphicsResetStatus() . This means that our
error checking can't call glGetError() in a loop without checking for
that return value and returning in that case.
https://bugzilla.gnome.org/show_bug.cgi?id=739178
|
|
|
|
|
|
|
| |
If the driver supports the GL_ARB_robustness extension we can expose
the graphics reset status this way.
https://bugzilla.gnome.org/show_bug.cgi?id=739178
|
|
|
|
|
|
|
| |
This adds API to allow callers to specify that they're interested in
video memory purge errors.
https://bugzilla.gnome.org/show_bug.cgi?id=739178
|
|
|
|
|
| |
Currently our private cogl/clutter forks still install tests as
cogl/clutter, which conflicts with the original libraries.
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=760439
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commit 188752158 changed cogl to stop needlessly creating its own
monitor output configuration when mutter would just soon overwrite
it anyway.
Unfortunately, that commit is causing a crash in some cases because
cogl will now create and later draw to a 0x0 egl surface until mutter
sets the monitor layout.
This commit changes cogl to avoid creating and using a surface, before
it knows how big of a surface to create.
https://bugzilla.gnome.org/show_bug.cgi?id=758073
|
|
|
|
|
|
|
| |
if mutter is handling the output setup, then we shouldn't do it,
too.
https://bugzilla.gnome.org/show_bug.cgi?id=758073
|
|
|
|
|
|
|
|
|
|
| |
If we get EACCES from drmPageFlip we're not going to get
a flip event and shouldn't wait for one.
This commit changes the EACCES path to silently ignore the
failed flip request and just clean up the fb.
https://bugzilla.gnome.org/show_bug.cgi?id=756926
|
|
|
|
| |
Return a boolean value, not NULL.
|
|
|
|
|
|
|
|
|
| |
ES3 provides glMapBufferRange as core, with the added bonus that it also
supports read mappings. Use this where possible.
Signed-off-by: Daniel Stone <daniels@collabora.com>
https://bugzilla.gnome.org/show_bug.cgi?id=728355
|