Skip to main content
GameDev.net gamedev.net
🔒 Locked

Qt doesn't recognize any OpenGL framebuffer functions

Started by Starshine_ May 17, 2008 at 3:41 PM 1 replies 1.2k views
Original Post
Starshine_
Starshine_
Hello! I'm having a weird problem when making an OpenGL program using Qt under Linux. It recognizes all OpenGL functions except ones which are used for framebuffers, such as glBindFramebufferEXT, glFramebufferTexture2DEXT, glGenRenderbuffersEXT, and other. I get an error like this for each one of them: error: 'glFramebufferTexture2DEXT' was not declared in this scope I have no idea what to do... do I need to include something more to be able to use them? I tried looking in the Qt documentation, but I haven't found anything that would explain this weird situation...
V-man
V-man
You can take a look at http://www.opengl.org/wiki/index.php/Getting_started

"OpenGL 2.0 and extensions" explains what you need to do.

Also, Qt is a kind of library for creating a window and creating a GL context among other things, just like GLUT is. I don't think you will find this kind of info in Qt documents.
Starshine_
Starshine_
Thanks! It's not working, though :( I installed glew and included it in my program with #include and now during compilation I get lots of errors such as this one:

/usr/include/GL/glew.h:8426: error: conflicting declaration 'typedef void (* PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, GLfloat*)'
/usr/include/GL/glext.h:5197: error: 'PFNGLFRAGMENTLIGHTFVSGIXPROC' has a previous declaration as 'typedef void (* PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, const GLfloat*)'

I've noticed in the Qt documentation here: http://doc.trolltech.com/4.3/qglcontext.html#getProcAddress that there's a function in Qt which returns a function pointer to OpenGL extensions functions, but it's not working... I get the error 'getProcAddress' was not declared in this scope. Even though other QGLContext functions like makeCurrent() are working well... :(

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.