mesa/src/gallium
Ross Burton 3ec07eaaa5 build: fix out-of-tree builds in gallium/auxiliary
The rules were writing files to e.g. util/u_indices_gen.py, but in an
out-of-tree build this directory doesn't exist in the build directory.  So,
create the directories just in case.

Cc: mesa-stable@lists.freedesktop.org
Reviewed-by: Matt Turner <mattst88@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
(cherry picked from commit 76feef0823)
2013-08-21 07:54:22 -07:00
..
auxiliary build: fix out-of-tree builds in gallium/auxiliary 2013-08-21 07:54:22 -07:00
docs gallium: Add PIPE_CAP_ENDIANNESS 2013-08-05 15:41:12 -07:00
drivers radeonsi: Always pre-load separate VGPRs for centroid vs. center interpolation 2013-08-21 07:54:18 -07:00
include st/dri: add a new driconf option disable_shader_bit_encoding for Unigine 2013-08-06 09:26:08 -07:00
state_trackers gallium/osmesa: add same checks to OSMesaMakeCurrent as the other osmesa 2013-08-21 07:54:13 -07:00
targets gallium/osmesa: link against static libglapi library too to get the gl exports 2013-08-21 07:54:09 -07:00
tests gallium/tests: fix the translate test 2013-06-28 09:43:17 -04:00
tools tools/trace: Return dummy fence object to silence warnings. 2013-07-01 12:06:58 +01:00
winsys r600g: disable GPUVM by default 2013-08-09 15:26:05 -07:00
Android.common.mk android: build gallium auxiliaries 2011-08-21 02:01:48 +08:00
Android.mk android: add ilo to the build system 2013-05-06 07:20:07 -07:00
Automake.inc Remove MESA_PIC_FLAGS macro 2013-01-10 22:01:31 +01:00
README.portability
SConscript Haiku: Add Gallium winsys and target code 2013-05-22 14:31:44 -05: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 u_memory.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.