> What are you referring to by "4.4 (or 4.5)"? XFree86 4.4.0 isn't out
> yet, so I'm assuming you do not mean XFree86.
Well, I did not follow at all XFree's development cycle lately. I was told
that the next major XFree tree would have this fixed. So it must be 4.4.0
:-)
> server glx vendor strin
Hi all,
first of all thanks for your comments on this.
Lionel: Just noticed I accidentially forgot to CC the list.
On Wed, Nov 19, 2003 at 11:04:00AM +0100, Lionel Ulmer wrote:
>
> It's a bug in the DRI libraries that I reported some time ago and should be
> fixed in the XFree 4.4 (or 4.5) rele
> No, your libGL seems to implement GLX1.4
It's still a bug regarding 'legacy' apps... The same way as if apps start to
stop reporting extensions that are now merged back into the main GL tree,
they will break all the apps written before the merge.
And last time I checked, the DRI implements GLX
On Tue, Nov 18, 2003 at 11:01:13PM +0100, Daniel Skorka wrote:
> The question I'm asking me now is:
> Is it a bug in my libGL because it is returning a wrong string, or
> is it a bug in wine because it is expecting something it shouldn't
> (there's a configure check for glXGetProcAddress as well)?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le Tuesday 18 November 2003 23:01, Daniel Skorka a écrit :
> Hi!
Hi,
> The question I'm asking me now is:
> Is it a bug in my libGL because it is returning a wrong string,
> or
No, your libGL seems to implement GLX1.4
> is it a bug in wine because
Hi!
I am having trouble with OpenGL under wine (specifically Half-Life). The
problem is some code in $(TOPDIR)/dlls/opengl32/wgl.c. The function
wglGetProcAddress would like to call glXGetProcAddressARB, but can't,
due to the DLL's initialisation routines, namely process_attach.
process_attach ca
