chromium-users

[Chromium-users] using chromium and glew?

[IOhannes m z. <zmo...@ie...>]

hi.

has anyone had success in using chromium with glew (the openGL
extensions wrangler library, a runtime checker for openGL extensions)?

it currently fails in glewInit().
however, it seems to work (without shaders, and rectangle textures and
stuff like this), if i just ignore the failed glewInit()...i don't know
whether this is such a good idea, though

i am not sure whether the problem is in glew or in chromium.


mfga.sdr
IOhannes

Re: [Chromium-users] using chromium and glew?

[IOhannes m z. <zmo...@ie...>]

IOhannes m zmoelnig wrote:
> hi.
> 
> has anyone had success in using chromium with glew (the openGL
> extensions wrangler library, a runtime checker for openGL extensions)?



btw, i am using glew-1.5 (statically linked into my app; sources build 
myself with extensions pulled from upstream) and chromium is pulled 
directly from CVS (so should be uptodate)

> 
> it currently fails in glewInit().
> however, it seems to work (without shaders, and rectangle textures and
> stuff like this), if i just ignore the failed glewInit()...i don't know
> whether this is such a good idea, though

after more tests it seems like GLSL-shaders do not work (i guess this is 
a chromium limitation), but ARB-shaders appear to work correctly.

i am on linux i386 (debian lenny/sid), my hardware is an nvidia G70 
(with the proprietary nvidia drivers 169.x)

mfg.asdr
IOhannes

Re: [Chromium-users] using chromium and glew?

[Alan H. <al...@tu...>]

On Mon, 2008-03-10 at 10:19 +0100, IOhannes m zmoelnig wrote:
> IOhannes m zmoelnig wrote:
> > hi.
> > 
> > has anyone had success in using chromium with glew (the openGL
> > extensions wrangler library, a runtime checker for openGL extensions)?
> 
> 
> 
> btw, i am using glew-1.5 (statically linked into my app; sources build 
> myself with extensions pulled from upstream) and chromium is pulled 
> directly from CVS (so should be uptodate)
> 
> > 
> > it currently fails in glewInit().
> > however, it seems to work (without shaders, and rectangle textures and
> > stuff like this), if i just ignore the failed glewInit()...i don't know
> > whether this is such a good idea, though
> 
> after more tests it seems like GLSL-shaders do not work (i guess this is 
> a chromium limitation), but ARB-shaders appear to work correctly.
> 
> i am on linux i386 (debian lenny/sid), my hardware is an nvidia G70 
> (with the proprietary nvidia drivers 169.x)

Chromium doesn't support OpenGL 2.x at this time.

Alan.

Re: [Chromium-users] using chromium and glew?

[IOhannes m z. <zmo...@ie...>]

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?


fgamsdr
IOhannes

Re: [Chromium-users] using chromium and glew?

[IOhannes m z. <zmo...@ie...>]

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

Re: [Chromium-users] using chromium and glew?

[Alan H. <al...@tu...>]

On Mon, 2008-03-10 at 14:10 +0100, IOhannes m zmoelnig wrote:
> 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.

I'd probably add the glX functions directly to getprocaddress.py, and
ignore APIspec.txt

Alan.

Re: [Chromium-users] using chromium and glew?

[IOhannes m z. <zmo...@ie...>]

Alan Hourihane wrote:

> Chromium doesn't support OpenGL 2.x at this time.

yes, i thought so.
however, this is not what bothers me. i am using glew exactly for this: 
to support backends that do not have specific extensions (e.g. 
openGL-2.x) without having to worry to much on my side.

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)

fmgasd.r
IOhannes

Re: [Chromium-users] using chromium and glew?

[Alan H. <al...@tu...>]

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.