2010-01-10 12:28:24 -05:00
|
|
|
/*
|
|
|
|
* Cogl
|
|
|
|
*
|
|
|
|
* An object oriented GL/GLES Abstraction/Utility Layer
|
|
|
|
*
|
|
|
|
* Copyright (C) 2010 Intel Corporation.
|
|
|
|
*
|
|
|
|
* This library is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU Lesser General Public
|
|
|
|
* License as published by the Free Software Foundation; either
|
|
|
|
* version 2 of the License, or (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This library is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
* Lesser General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU Lesser General Public
|
2010-03-01 07:56:10 -05:00
|
|
|
* License along with this library. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*
|
|
|
|
*
|
2010-01-10 12:28:24 -05:00
|
|
|
*
|
|
|
|
* Authors:
|
|
|
|
* Damien Lespiau <damien.lespiau@intel.com>
|
2010-07-03 19:18:10 -04:00
|
|
|
* Robert Bragg <robert@linux.intel.com>
|
2010-01-10 12:28:24 -05:00
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef __COGL_BUFFER_PRIVATE_H__
|
|
|
|
#define __COGL_BUFFER_PRIVATE_H__
|
|
|
|
|
|
|
|
#include <glib.h>
|
|
|
|
|
2010-10-27 13:54:57 -04:00
|
|
|
#include "cogl-object-private.h"
|
2010-01-10 12:28:24 -05:00
|
|
|
#include "cogl-buffer.h"
|
2012-02-17 20:19:17 -05:00
|
|
|
#include "cogl-context.h"
|
2012-03-23 14:05:46 -04:00
|
|
|
#include "cogl-gl-header.h"
|
2010-01-10 12:28:24 -05:00
|
|
|
|
|
|
|
G_BEGIN_DECLS
|
|
|
|
|
|
|
|
typedef struct _CoglBufferVtable CoglBufferVtable;
|
|
|
|
|
|
|
|
struct _CoglBufferVtable
|
|
|
|
{
|
2010-11-04 12:01:23 -04:00
|
|
|
void * (* map) (CoglBuffer *buffer,
|
|
|
|
CoglBufferAccess access,
|
|
|
|
CoglBufferMapHint hints);
|
2010-01-10 12:28:24 -05:00
|
|
|
|
2010-07-03 19:18:10 -04:00
|
|
|
void (* unmap) (CoglBuffer *buffer);
|
2010-01-10 12:28:24 -05:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool (* set_data) (CoglBuffer *buffer,
|
2010-07-03 19:18:10 -04:00
|
|
|
unsigned int offset,
|
2010-11-04 12:01:23 -04:00
|
|
|
const void *data,
|
2010-07-03 19:18:10 -04:00
|
|
|
unsigned int size);
|
2010-01-10 12:28:24 -05:00
|
|
|
};
|
|
|
|
|
|
|
|
typedef enum _CoglBufferFlags
|
|
|
|
{
|
2011-01-13 10:35:30 -05:00
|
|
|
COGL_BUFFER_FLAG_NONE = 0,
|
|
|
|
COGL_BUFFER_FLAG_BUFFER_OBJECT = 1UL << 0, /* real openGL buffer object */
|
|
|
|
COGL_BUFFER_FLAG_MAPPED = 1UL << 1,
|
|
|
|
COGL_BUFFER_FLAG_MAPPED_FALLBACK = 1UL << 2
|
2010-01-10 12:28:24 -05:00
|
|
|
} CoglBufferFlags;
|
|
|
|
|
2010-07-03 16:30:33 -04:00
|
|
|
typedef enum {
|
|
|
|
COGL_BUFFER_USAGE_HINT_TEXTURE,
|
2011-03-02 10:01:41 -05:00
|
|
|
COGL_BUFFER_USAGE_HINT_ATTRIBUTE_BUFFER,
|
2011-03-02 18:31:19 -05:00
|
|
|
COGL_BUFFER_USAGE_HINT_INDEX_BUFFER
|
2010-07-03 16:30:33 -04:00
|
|
|
} CoglBufferUsageHint;
|
|
|
|
|
2010-07-05 18:24:34 -04:00
|
|
|
typedef enum {
|
|
|
|
COGL_BUFFER_BIND_TARGET_PIXEL_PACK,
|
|
|
|
COGL_BUFFER_BIND_TARGET_PIXEL_UNPACK,
|
2011-03-02 10:01:41 -05:00
|
|
|
COGL_BUFFER_BIND_TARGET_ATTRIBUTE_BUFFER,
|
2011-03-02 18:31:19 -05:00
|
|
|
COGL_BUFFER_BIND_TARGET_INDEX_BUFFER,
|
2010-07-05 18:24:34 -04:00
|
|
|
|
|
|
|
COGL_BUFFER_BIND_TARGET_COUNT
|
|
|
|
} CoglBufferBindTarget;
|
|
|
|
|
2010-01-10 12:28:24 -05:00
|
|
|
struct _CoglBuffer
|
|
|
|
{
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglObject _parent;
|
2012-02-06 12:08:58 -05:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglContext *context;
|
2012-02-06 12:08:58 -05:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBufferVtable vtable;
|
2010-01-10 12:28:24 -05:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBufferBindTarget last_target;
|
2010-07-05 18:24:34 -04:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBufferFlags flags;
|
2010-01-10 12:28:24 -05:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
GLuint gl_handle; /* OpenGL handle */
|
|
|
|
unsigned int size; /* size of the buffer, in bytes */
|
|
|
|
CoglBufferUsageHint usage_hint;
|
|
|
|
CoglBufferUpdateHint update_hint;
|
2010-01-10 12:28:24 -05:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
/* points to the mapped memory when the CoglBuffer is a VBO, PBO,
|
|
|
|
* ... or points to allocated memory in the fallback paths */
|
|
|
|
uint8_t *data;
|
2010-10-26 11:06:46 -04:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
int immutable_ref;
|
2010-10-26 14:08:51 -04:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
unsigned int store_created:1;
|
2010-01-10 12:28:24 -05:00
|
|
|
};
|
|
|
|
|
2010-07-03 18:56:44 -04:00
|
|
|
/* This is used to register a type to the list of handle types that
|
|
|
|
will be considered a texture in cogl_is_texture() */
|
|
|
|
void
|
2012-01-24 11:24:26 -05:00
|
|
|
_cogl_buffer_register_buffer_type (const CoglObjectClass *klass);
|
2010-07-03 18:56:44 -04:00
|
|
|
|
|
|
|
#define COGL_BUFFER_DEFINE(TypeName, type_name) \
|
|
|
|
COGL_OBJECT_DEFINE_WITH_CODE \
|
|
|
|
(TypeName, type_name, \
|
2012-01-24 11:24:26 -05:00
|
|
|
_cogl_buffer_register_buffer_type (&_cogl_##type_name##_class))
|
2010-07-03 18:56:44 -04:00
|
|
|
|
2010-07-03 19:18:10 -04:00
|
|
|
void
|
|
|
|
_cogl_buffer_initialize (CoglBuffer *buffer,
|
2012-02-06 12:08:58 -05:00
|
|
|
CoglContext *context,
|
2010-07-03 19:18:10 -04:00
|
|
|
unsigned int size,
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool use_malloc,
|
2010-07-05 18:24:34 -04:00
|
|
|
CoglBufferBindTarget default_target,
|
2010-07-03 19:18:10 -04:00
|
|
|
CoglBufferUsageHint usage_hint,
|
|
|
|
CoglBufferUpdateHint update_hint);
|
2010-07-03 18:56:44 -04:00
|
|
|
|
2010-07-03 19:18:10 -04:00
|
|
|
void
|
|
|
|
_cogl_buffer_fini (CoglBuffer *buffer);
|
|
|
|
|
2010-10-12 08:14:17 -04:00
|
|
|
void *
|
2010-07-03 19:18:10 -04:00
|
|
|
_cogl_buffer_bind (CoglBuffer *buffer,
|
2010-07-05 18:24:34 -04:00
|
|
|
CoglBufferBindTarget target);
|
|
|
|
|
|
|
|
void
|
|
|
|
_cogl_buffer_unbind (CoglBuffer *buffer);
|
2010-07-03 16:30:33 -04:00
|
|
|
|
|
|
|
CoglBufferUsageHint
|
|
|
|
_cogl_buffer_get_usage_hint (CoglBuffer *buffer);
|
|
|
|
|
2010-07-03 19:18:10 -04:00
|
|
|
GLenum
|
|
|
|
_cogl_buffer_access_to_gl_enum (CoglBufferAccess access);
|
|
|
|
|
2010-10-26 14:08:51 -04:00
|
|
|
CoglBuffer *
|
|
|
|
_cogl_buffer_immutable_ref (CoglBuffer *buffer);
|
|
|
|
|
|
|
|
void
|
|
|
|
_cogl_buffer_immutable_unref (CoglBuffer *buffer);
|
|
|
|
|
2011-01-13 10:35:30 -05:00
|
|
|
/* This is a wrapper around cogl_buffer_map for internal use when we
|
|
|
|
want to map the buffer for write only to replace the entire
|
|
|
|
contents. If the map fails then it will fallback to writing to a
|
|
|
|
temporary buffer. When _cogl_buffer_unmap_for_fill_or_fallback is
|
|
|
|
called the temporary buffer will be copied into the array. Note
|
|
|
|
that these calls share a global array so they can not be nested. */
|
|
|
|
void *
|
|
|
|
_cogl_buffer_map_for_fill_or_fallback (CoglBuffer *buffer);
|
|
|
|
|
|
|
|
void
|
|
|
|
_cogl_buffer_unmap_for_fill_or_fallback (CoglBuffer *buffer);
|
|
|
|
|
2010-01-10 12:28:24 -05:00
|
|
|
G_END_DECLS
|
|
|
|
|
|
|
|
#endif /* __COGL_BUFFER_PRIVATE_H__ */
|