-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 25 May 2004 23:43, Maurice van der Pot wrote:
> The modifications I made to the driver were visible when I executed an
> OpenGL app, so I knew it was using the right r200_dri.so. Strangely,
> I was unable to get most of the debug prints wor
Maurice van der Pot wrote:
On Mon, May 24, 2004 at 08:54:27AM -0700, Ian Romanick wrote:
For a developer, the best bet is to get the DRI tree and the Mesa tree.
Build the DRI tree and do a 'make install' as root *once*.
The thing is that I didn't want to modify (pollute? ruin?) my working X
ins
Thanks for your response Ian.
On Mon, May 24, 2004 at 08:54:27AM -0700, Ian Romanick wrote:
>
> How are you building? Are you building everything in the DRI tree?
> libGL in the DRI tree and the drivers in the Mesa tree? The libGL built
> in the Mesa tree is *NOT* the one used with the DRI dr
Maurice van der Pot wrote:
I have just started looking into DRI development and I have been experiencing
some difficulties using gdb. For example, I cannot currently step into
functions of libGL (it was compiled with debug info and LD_LIBRARY_PATH is
set correctly). Another thing is that the symb
Hello,
I have just started looking into DRI development and I have been experiencing
some difficulties using gdb. For example, I cannot currently step into
functions of libGL (it was compiled with debug info and LD_LIBRARY_PATH is
set correctly). Another thing is that the symbols from r200_dri.s
