mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2025-12-28 06:00:10 +01:00
a57f842519
That is, remove pipe_context::draw_arrays, pipe_context::draw_elements, pipe_context::draw_arrays_instanced, pipe_context::draw_elements_instanced, pipe_context::draw_range_elements. |
||
|---|---|---|
| .. | ||
| Makefile | ||
| rbug_context.c | ||
| rbug_context.h | ||
| rbug_core.c | ||
| rbug_objects.c | ||
| rbug_objects.h | ||
| rbug_public.h | ||
| rbug_screen.c | ||
| rbug_screen.h | ||
| README | ||
| SConscript | ||
RBUG PIPE DRIVER = About = This directory contains a Gallium3D remote debugger pipe driver. It provides remote debugging functionality. = Build Instructions = To build, invoke scons on the top dir as scons dri=no statetrackers=mesa winsys=xlib = Usage = To use do export LD_LIBRARY_PATH=$PWD/build/linux-x86-debug/lib ensure the right libGL.so is being picked by doing ldd progs/trivial/tri export XMESA_TRACE=y 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 <jrfonseca@tungstengraphics.com> Jakob Bornecrantz <jakob@vmware.com>