---------- Forwarded message ----------
From: Nishikant Deshmukh <firstname.lastname@example.org>
Date: Thu, Mar 17, 2011 at 6:05 AM
Subject: Re: [glew-users] Compiling GLEW on Qt Windows
I could compile the library using mingw by manually changing the Makefile to use mingw as SYSTEM.
My program compiles only with the resulting file libglew32.dll.a for some reason.
When I run my program it fails on glGenFramebuffersEXT
when I put this codeif (
cout<<"Old EXT FBO available"<<endl;
cout<<"Old EXT FBO NOT available"<<endl;
cout<<"Newer ARB FBO available"<<endl;
cout<<"Old ARB FBO NOT available"<<endl;
Old EXT FBO NOT available
Old ARB FBO NOT available
Initially I thought my graphics card don't support it
but I installed Linux and it runs just fine. (Sorry Quadroplex 5800, I doubted you).
attached is the glewinfo.txt and it shows no issues.
Can someone tell me what might be happening?
Best Regards,Nishikant Deshmukh
On Mon, Feb 28, 2011 at 2:27 AM, Stig Hornang <email@example.com>
My experience points out that when you get prefixed "_imp__" strings
in the unresolved symbol messages, this means that your trying to use
an import library (.lib or .a file) created by Visual Studio C++ in a
In my case I downloaded the glew source and compiled the library
myself - either using msys or cmake or whatever build system that
comes with the glew source, don't remember which one it was. You can
probably also use the mingw gcc that follows Qt
(c:\Qt\2010.xx\mingw\bin\ming32-gcc.exe) and compile it on the windows
The other, and usually more non-friendly option (required when you're
using closed source libraries) is to recreate the import library using
various tools like dumpbin.exe (VC++ tool), psexports.exe, dlltool
(mingw tool), to create an import library that works with GCC.