[GEM-dev] GLEWified

Alex Norman alex at neisis.net
Mon Mar 10 02:18:46 CET 2008


If possible it would be good to keep the ability to do a compile time switch to
disable shaders even if your hardware supports it as chromium does not support
shaders [which make sense as it is distributed over several computers] and it
would be nice to retain chromium support.

-Alex

On  0, IOhannes m zmoelnig <zmoelnig at iem.at> wrote:
> so i since today Gem depends on glew, the "openGL Extension Wrangler", a 
>   runtime openGL extension checker.
> 
> this basically means, that Gem now does runtime checks, whether your 
> graphics card supports a certain feature (e.g. GLSL shaders) instead of 
> making decisions at compiletime.
> 
> this should magically solve all the problems people kept having with 
> certain openGL-functions not being found when trying to load Gem.
> 
> it should also make the "--disable-ARB", "--disable-NV" and 
> "--with-glversion=" flags to configure obsolete.
> 
> Gem has the sourcecode of glew included (so you don't need to install it 
> separately) and links statically to it.
> 
> 
> for now, all (or most?) objects that had compile-time openGL checks 
> should now have runtime checks (probably i have forgotten some, who knows)
> 
> 
> 
> i have successfully compiled it on linux/debian and osx-10.4.
> i have successfully tested it on debian(lenny/sid) with nvidia (GeForce 
> 7800 GTX; proprietary drivers v169) and on debian(etch) with ati (Rage 
> Mobility P/M; old "ati" xorg drivers; mesa-6.5.1)
> 
> please test!
> (especially specialized functions, like texture, glsl and othe shaders, 
> framebuffer)
> 
> mfga.ds
> IOhannes
> 
> 
> PS: i have for know purged pix_texture support for outdated 
> openGL-versions (like openGL<1.1)
> 
> _______________________________________________
> GEM-dev mailing list
> GEM-dev at iem.at
> http://lists.puredata.info/listinfo/gem-dev




More information about the GEM-dev mailing list