On Wed, Mar 3, 2010 at 4:55 AM, Stefan Dösinger wrote:
>
> Am 02.03.2010 um 18:39 schrieb Henri Verbeet:
>> (I also still haven't seen anyone make a *convincing* argument for why
>> we'd want to have a "somewhat working, but not quite" wined3d if we
>> don't have OpenGL in the first place.)
> In t
Am 02.03.2010 um 18:39 schrieb Henri Verbeet:
> (I also still haven't seen anyone make a *convincing* argument for why
> we'd want to have a "somewhat working, but not quite" wined3d if we
> don't have OpenGL in the first place.)
In the past there have been two reasons:
*) Gentoo users "OMG I don
On Wed, Mar 3, 2010 at 8:14 AM, Kusanagi Kouichi wrote:
> On 2010-03-02 18:06:00 +0100, Roderick Colenbrander wrote:
>> In what situation does it exactly crash for you? Is it crashing
>> because there is no libGL around? I'm not sure what the right thing to
>> do is. Due to it our wglGetProcAddres
On 2010-03-02 18:06:00 +0100, Roderick Colenbrander wrote:
> In what situation does it exactly crash for you? Is it crashing
> because there is no libGL around? I'm not sure what the right thing to
> do is. Due to it our wglGetProcAddress won't function because it
> relies on glXGetProcAddress.
>
On 2 March 2010 18:06, Roderick Colenbrander wrote:
> I'm not sure about the shader backend part of the patch (I don't know
> that code well), so I'm leaving that to Henri and Stefan.
>
You shouldn't be calling those if there's no GL.
(I also still haven't seen anyone make a *convincing* argument
In what situation does it exactly crash for you? Is it crashing
because there is no libGL around? I'm not sure what the right thing to
do is. Due to it our wglGetProcAddress won't function because it
relies on glXGetProcAddress.
Our use of wglGetProcAddress isn't correct (but it works on WINE :))
