mesa/src/gallium
Brian Paul 7d7f3e2c94 gallium: split long prims into chunks with an even number of vertices
This fixes culling "parity" errors when splitting long tri strips.  Splitting
strips into chunks with an odd number of vertices causes front/back-face
orientation to get reversed and upsets culling.
2008-06-18 14:55:12 -06:00
..
auxiliary gallium: split long prims into chunks with an even number of vertices 2008-06-18 14:55:12 -06:00
drivers i915: Fix for s8_z24 textures not being shown 2008-06-18 01:48:24 +02:00
include/pipe gallium: Remove PIPE_FORMAT_A8UB8UG8SR8S_NORM definition. 2008-06-18 08:51:38 +02:00
state_trackers Code reorganization: placeholder for state-trackers. 2008-02-15 17:52:14 +09:00
winsys egl: omit libmesa.a glapi.c from library 2008-06-18 09:22:01 -06:00
Makefile i915: Moved pipe_buffer and i915_winsys functions to a common folder 2008-06-06 14:49:02 +02:00
Makefile.template Remove src/mesa and src/mesa/main from gallium source include paths. 2008-02-19 15:07:53 +09:00
README.portability gallium: Fix typo. 2008-05-19 15:01:17 +09:00
SConscript gallium: Build and link the translate module. 2008-04-16 11:39:22 +09:00

	      CROSS-PLATFORM PORTABILITY GUIDELINES FOR GALLIUM3D 


= General Considerations =

The state tracker and winsys driver support a rather limited number of
platforms. However, the pipe drivers are meant to run in a wide number of
platforms. Hence the pipe drivers, the auxiliary modules, and all public
headers in general, should strictly follow these guidelines to ensure


= Compiler Support =

* Include the p_compiler.h.

* Don't use the 'inline' keyword, use the INLINE macro in p_compiler.h instead.

* Cast explicitly when converting to integer types of smaller sizes.

* Cast explicitly when converting between float, double and integral types.

* Don't use named struct initializers.

* Don't use variable number of macro arguments. Use static inline functions
instead.

* Don't use C99 features.

= Standard Library =

* Avoid including standard library headers. Most standard library functions are
not available in Windows Kernel Mode. Use the appropriate p_*.h include.

== Memory Allocation ==

* Use MALLOC, CALLOC, FREE instead of the malloc, calloc, free functions.

* Use align_pointer() function defined in p_util.h for aligning pointers in a
portable way.

== Debugging ==

* Use the functions/macros in p_debug.h.

* Don't include assert.h, call abort, printf, etc.


= Code Style =

== Inherantice in C ==

The main thing we do is mimic inheritance by structure containment.

Here's a silly made-up example:

/* base class */
struct buffer
{
  int size;
  void (*validate)(struct buffer *buf);
};

/* sub-class of bufffer */
struct texture_buffer
{
  struct buffer base;  /* the base class, MUST COME FIRST! */
  int format;
  int width, height;
};


Then, we'll typically have cast-wrapper functions to convert base-class 
pointers to sub-class pointers where needed:

static inline struct vertex_buffer *vertex_buffer(struct buffer *buf)
{
  return (struct vertex_buffer *) buf;
}


To create/init a sub-classed object:

struct buffer *create_texture_buffer(int w, int h, int format)
{
  struct texture_buffer *t = malloc(sizeof(*t));
  t->format = format;
  t->width = w;
  t->height = h;
  t->base.size = w * h;
  t->base.validate = tex_validate;
  return &t->base;
}

Example sub-class method:

void tex_validate(struct buffer *buf)
{
  struct texture_buffer *tb = texture_buffer(buf);
  assert(tb->format);
  assert(tb->width);
  assert(tb->height);
}


Note that we typically do not use typedefs to make "class names"; we use
'struct whatever' everywhere.

Gallium's pipe_context and the subclassed psb_context, etc are prime examples 
of this.  There's also many examples in Mesa and the Mesa state tracker.