Re: WINED3D: Fix compilation (VBO constants)

[Stefan Dösinger]

Am Dienstag 27 Juni 2006 00:32 schrieb H. Verbeet:
> This makes wined3d use the VBO constants as defined in
> include/wine/wined3d_gl.h
> Just asking, how do you check for those constant? As the code I sent compiled 
> fine here(with mesa) the way I used is to look at the diff if some changes 
> are missing the _ARB or GL_EXTCALL. Apparently that is prone to errors and I 
> miss some all the time.

WINED3D: Fix compilation (VBO constants)

[James Hawkins]

On 6/27/06, Stefan Dösinger <stefandoesinger(a)gmx.at> wrote:
> Am Dienstag 27 Juni 2006 00:32 schrieb H. Verbeet:
> > This makes wined3d use the VBO constants as defined in
> > include/wine/wined3d_gl.h
>
> Just asking, how do you check for those constant? As the code I sent compiled
> fine here(with mesa) the way I used is to look at the diff if some changes
> are missing the _ARB or GL_EXTCALL. Apparently that is prone to errors and I
> miss some all the time.

He reads my complaints :)

http://winehq.org/pipermail/wine-devel/2006-June/049004.html

-- 
James Hawkins

WINED3D: Fix compilation (VBO constants)

[H. Verbeet]

On 27/06/06, Stefan Dösinger <stefandoesinger(a)gmx.at> wrote:
> Am Dienstag 27 Juni 2006 00:32 schrieb H. Verbeet:
> > This makes wined3d use the VBO constants as defined in
> > include/wine/wined3d_gl.h
> > Just asking, how do you check for those constant? As the code I sent compiled
> > fine here(with mesa) the way I used is to look at the diff if some changes
> > are missing the _ARB or GL_EXTCALL. Apparently that is prone to errors and I
> > miss some all the time.
> > A lot of those you can spot just by looking at the diff, yes. However,
> > I've also got a Debian stable machine on which I try compilation from
> > time to time.