mesa/src/gallium/drivers/rbug
Dylan Baker 4d701ee969 meson: build gallium helper drivers
This builds ddebug, noop, rbug, and trace drivers.

Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com>
Reviewed-by: Eric Anholt <eric at anholt.net>
2017-10-16 16:32:43 -07:00
..
Makefile.am gallium/rbug: ship all files in the tarball 2014-09-05 23:46:26 +01:00
Makefile.sources gallium/rbug: ship all files in the tarball 2014-09-05 23:46:26 +01:00
meson.build meson: build gallium helper drivers 2017-10-16 16:32:43 -07:00
rbug_context.c gallium: remove pipe_index_buffer and set_index_buffer 2017-05-10 19:00:16 +02:00
rbug_context.h gallium/util: replace pipe_condvar with cnd_t 2017-03-07 09:07:33 +11:00
rbug_core.c gallium: decrease the size of pipe_resource - 64 -> 48 bytes 2017-04-04 11:14:43 +02:00
rbug_objects.c gallium/drivers: Trivial code-style cleanup 2015-12-06 17:10:22 +01:00
rbug_objects.h gallium: replace INLINE with inline 2015-07-21 17:52:16 -04:00
rbug_public.h gallium/drivers: Add extern "C" wrappers to public entry 2015-05-15 13:55:59 -04:00
rbug_screen.c gallium: add pipe_screen::check_resource_capability 2017-10-12 19:03:33 +02:00
rbug_screen.h gallium/util: replace pipe_mutex_unlock() with mtx_unlock() 2017-03-07 08:53:05 +11:00
README
SConscript

                              RBUG PIPE DRIVER


= About =

This directory contains a Gallium3D remote debugger pipe driver.
It provides remote debugging functionality.


= Usage =

Do

   GALLIUM_RBUG=true progs/trivial/tri

which should open gallium remote debugging session. While the program is running
you can launch the small remote debugging application from progs/rbug. More
information is in that directory. Also for a gui see:

   http://cgit.freedesktop.org/mesa/rbug-gui


= Integrating =

You can integrate the rbug pipe driver either inside the state tracker or the 
target. The procedure on both cases is the same. Let's assume you have a 
pipe_screen obtained by the usual means (variable and function names are just
for illustration purposes):

  real_screen = real_screen_create(...);

The rbug screen is then created by doing

  rbug_screen = rbug_screen_create(real_screen);

You can then simply use rbug_screen instead of real_screen.

You can create as many contexts you wish from rbug_screen::context_create they
are automatically wrapped by rbug_screen.


--
Jose Fonseca <jfonseca@vmware.com>
Jakob Bornecrantz <jakob@vmware.com>