Re: using chromium and glew?

Alan Hourihane wrote:
> 
> 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.

a thanks for the hint.

so what is the best way for me to proceed?
i just added all of the glX functions to opengl_stub/getprocaddress.c, 
just to discover (when i was about to send a diff) that getprocaddress.c 
is generated by getprocaddress.py (yea, now i know that i should have 
read the boilerplate of getprocaddress.c!), which uses 
glapi_parser/APIspec.txt to know what to generate.

should i put glX directly into getprocaddress.py, or should i create 
definitions in glapi_parser/APIspec.txt.

or is this totally the wrong way to do it? (e.g. because there are no 
plans in chromium for what i would like to have)


mfg.adsr
IOhannes

PS: adding the glX-functions to the getprocaddress indeed did the trick 
and everything went smoothly...

-------------------------------------------------------------------------
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/