Re: [PD] GEM and chromium

2007-06-17 Thread Alex
Recently I have been successful getting Gem running over Chromium:
http://chromium.sourceforge.net/

After picking up from where august left of, disabling all of the
non-chromium compatible extensions I could via compile time flags :
  ./configure --with-glversion=1.5 --disable-ARB --disable-NV

I was still having problems with glDeleteFramebuffersEXT and other frame buffer
commands not being defined when I ran via chromium.

I didn't see a compile option that allowed me to disable these frame buffer
commands, so I added this:

#undef GL_EXT_framebuffer_object

to src/Controls/gemframebuffer.cpp

after the includes.

and now gem works via chromium.  Maybe the Gem developers could add [or suggest
one that already exists] a compile time option to disable these commands, so
that others might be able to use chromium with gem as well.

-Alex
btw, I've sent this info to the GEM list as well but figured it might
be useful for some people on here as well.

On 5/15/07, august [EMAIL PROTECTED] wrote:
  On Tue, 2007-05-15 at 20:16 +0200, august wrote:
  
   I am currently trying to compile GEM CVS so that it is compatible with the
   current version of Chromium (1.9), and am having trouble getting the
   Gem.lib to load while chromium is faking the opengl calls.  Has anyone
   gotten this to work already?
  
   Without using the Chromium environment, PD runs fine with GEM on the
   mothership.   But, when I try to run PD/GEM under Chromium, I get
   library loading errors for things like : glGetShaderInfoLog,
   glDeleteProgram, etc.)
  
   Is there a way to compile GEM without glsl support entirely?  I can't
   find any way to ./configure it so that glsl is disabled.
  
   I'm pretty confident this should fly, just need to ditch the glsl.
 
  try:
 
  ./configure --with-glversion=1.5
 
  at least, that helped here, since my ati card doesn't seem to support
  glsl as well.
 
  roman


 thanks!  that got me past that part.

 now I am having problems with framebuffer extenstions
 (glCheckFramebufferStatusEXT, etc)

 any way to turn this off at compile?



 ___
 PD-list@iem.at mailing list
 UNSUBSCRIBE and account-management - 
 http://lists.puredata.info/listinfo/pd-list


___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


[PD] GEM and chromium

2007-05-15 Thread august


I am currently trying to compile GEM CVS so that it is compatible with the
current version of Chromium (1.9), and am having trouble getting the
Gem.lib to load while chromium is faking the opengl calls.  Has anyone
gotten this to work already?

Without using the Chromium environment, PD runs fine with GEM on the
mothership.   But, when I try to run PD/GEM under Chromium, I get
library loading errors for things like : glGetShaderInfoLog,
glDeleteProgram, etc.)   

Is there a way to compile GEM without glsl support entirely?  I can't
find any way to ./configure it so that glsl is disabled.

I'm pretty confident this should fly, just need to ditch the glsl.

thanks -august. 

___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] GEM and chromium

2007-05-15 Thread Roman Haefeli
On Tue, 2007-05-15 at 20:16 +0200, august wrote:
 
 I am currently trying to compile GEM CVS so that it is compatible with the
 current version of Chromium (1.9), and am having trouble getting the
 Gem.lib to load while chromium is faking the opengl calls.  Has anyone
 gotten this to work already?
 
 Without using the Chromium environment, PD runs fine with GEM on the
 mothership.   But, when I try to run PD/GEM under Chromium, I get
 library loading errors for things like : glGetShaderInfoLog,
 glDeleteProgram, etc.)   
 
 Is there a way to compile GEM without glsl support entirely?  I can't
 find any way to ./configure it so that glsl is disabled.
 
 I'm pretty confident this should fly, just need to ditch the glsl.

try:

./configure --with-glversion=1.5

at least, that helped here, since my ati card doesn't seem to support
glsl as well.

roman






___ 
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: 
http://mail.yahoo.de


___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] GEM and chromium

2007-05-15 Thread august
 On Tue, 2007-05-15 at 20:16 +0200, august wrote:
  
  I am currently trying to compile GEM CVS so that it is compatible with the
  current version of Chromium (1.9), and am having trouble getting the
  Gem.lib to load while chromium is faking the opengl calls.  Has anyone
  gotten this to work already?
  
  Without using the Chromium environment, PD runs fine with GEM on the
  mothership.   But, when I try to run PD/GEM under Chromium, I get
  library loading errors for things like : glGetShaderInfoLog,
  glDeleteProgram, etc.)   
  
  Is there a way to compile GEM without glsl support entirely?  I can't
  find any way to ./configure it so that glsl is disabled.
  
  I'm pretty confident this should fly, just need to ditch the glsl.
 
 try:
 
 ./configure --with-glversion=1.5
 
 at least, that helped here, since my ati card doesn't seem to support
 glsl as well.
 
 roman


thanks!  that got me past that part.

now I am having problems with framebuffer extenstions
(glCheckFramebufferStatusEXT, etc)

any way to turn this off at compile?



___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list