From: Alan Wu <al...@au...> - 2010-03-17 03:59:38
|
Hi all, I have built and compiled a linux-x86-32 shared object library of Mesa7.7 under Ubuntu8.04, both glxinfo and glewinfo show me that glBlitFramebufferEXT is available however I got the undefined reference error message when I call the function in my program. I also could not find "glBlitFramebufferEXT" when ran a "objdump -x" command on the built library. I am planning to do a MSAA with framebuffer object and I was very excited to find that glRenderBufferStorageMultisampleEXT is now supported. Great work! Anyway, I greatly appreciate any suggestion that you guys may have. I thought GL_EXT_framebuffer_blit is supported since Mesa6.5. Thanks so much for your time. Kind Regards, Alan |
From: tom f. <tf...@al...> - 2010-03-17 04:18:24
|
Alan Wu <al...@au...> writes: > I have built and compiled a linux-x86-32 shared object library > of Mesa7.7 under Ubuntu8.04, both glxinfo and glewinfo show me > that glBlitFramebufferEXT is available however I got the undefined > reference error message when I call the function in my program. I > also could not find "glBlitFramebufferEXT" when ran a "objdump -x" > command on the built library. It's just "glBlitFramebuffer" if you're going to call it directly. At least, that holds with my build of semi-recent master.. If you want to load it dynamically, I would bet that 'glXGetProcAddressARB("glBlitFramebufferEXT");' works; leaving off the EXT should work too, of course. It shows up in glewinfo because GLEW *is* loading it dynamically. I'd recommend you just use GLEW yourself; you don't want rely on an extension being available at compilation time, anyway. Even if your program is worthless without the extension, at least you'll have enough control to pop up a semi-useful error message. Cheers, -tom |
From: Alan Wu <al...@au...> - 2010-03-17 22:13:51
|
tom fogal wrote: > Alan Wu <al...@au...> writes: >> I have built and compiled a linux-x86-32 shared object library >> of Mesa7.7 under Ubuntu8.04, both glxinfo and glewinfo show me >> that glBlitFramebufferEXT is available however I got the undefined >> reference error message when I call the function in my program. I >> also could not find "glBlitFramebufferEXT" when ran a "objdump -x" >> command on the built library. > > It's just "glBlitFramebuffer" if you're going to call it directly. At > least, that holds with my build of semi-recent master.. > > If you want to load it dynamically, I would bet that > 'glXGetProcAddressARB("glBlitFramebufferEXT");' works; leaving off the > EXT should work too, of course. > > It shows up in glewinfo because GLEW *is* loading it dynamically. > > I'd recommend you just use GLEW yourself; you don't want rely on an > extension being available at compilation time, anyway. Even if your > program is worthless without the extension, at least you'll have enough > control to pop up a semi-useful error message. > > Cheers, > > -tom Thanks Tom, I am considering using GLEW too, at this moment we handle loading the headers ourselves, perhaps should let GLEW to do it instead. Interestingly, I have built Mesa7.7 on both 32 and 64 bit machine and glBlitFramebuffer is only defined on the 64bit built. Cheers, Alan |