Re: using chromium and glew?

On Mon, 2008-03-10 at 12:16 +0100, IOhannes m zmoelnig wrote:
> IOhannes m zmoelnig wrote:
> > Alan Hourihane wrote:
> 
> > that is why i try to find out why glewInit() claims to fail (read: not 
> > being able to determine which extensions are/openGL version is supported)
> 
> ok, i was able to narrow the problem down.
> 
> the problem is in some glx-initialisation routine.
> glew tries to get the pointer to glXGetCurrentDisplay() by issuing
>     glXGetProcAddressARB((const GLubyte*)"glXGetCurrentDisplay")
> 
> on my normal system (without chromium) this returns the address of the 
> function call.
> when running chromium, this calls returns 0
> 
> 
> luckily (for me) i currently don't use the glx extension wrangler of 
> GLEW, so i have no _real_ problems.
> 
> nevertheless i am wondering, why i don't get the correct address when 
> using chromium (i guess it will turn into a problem, once somebody wants 
> to use glew for glx extension checking in combination with chromium)
> 
> any hints?

In the opengl_stub/getprocaddress.py code we never return any glX*() 
functions for glXGetProcAddress() which actually translates into
crGetProcAddress().

It's should just be a matter of adding glX*() functions to this so 
that Chromium can return the appropriate address.

Alan.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/