SFML community forums

Help => General => Topic started by: GLS on May 12, 2014, 05:09:38 pm

Title: GLEW warnings
Post by: GLS on May 12, 2014, 05:09:38 pm

Hello! Sorry for my english. I use Google Translate.
I downloaded GLEW 1.10.0 and added path c:\glew\include in code::blocks Build options -> Search directories.
main.cpp

#define GLEW_STATIC
#include <GL/glew.h>
#include <SFML/Graphics.hpp>
//.............
int main()
{
    GLenum err = glewInit();
    if (GLEW_OK != err)
    {
        fprintf(stderr, "Error: %s\n", glewGetErrorString(err));
        return 1;
    }

    fprintf(stdout, "Status: Using GLEW %s\n", glewGetString(GLEW_VERSION));
    //..........
}
 

The application compiles, but a warnings is issued:
Warning: resolving _glewInit@0 by linking to _glewInit
Warning: resolving _glewGetString@4 by linking to _glewGetString
Warning: resolving _glewGetErrorString@4 by linking to _glewGetErrorString
Prompt please, what's the problem?

Title: AW: GLEW warnings
Post by: eXpl0it3r on May 12, 2014, 05:27:15 pm

SFML uses GLEW as well, thus the linker might issue a warning.

At best you could build SFML statically and link glew statically once (only possible with the latest SFML version from GitHib).

Title: Re: AW: GLEW warnings
Post by: GLS on May 12, 2014, 05:42:36 pm

Quote from: eXpl0it3r on May 12, 2014, 05:27:15 pm

SFML uses GLEW as well, thus the linker might issue a warning.

I know, in my application SFML linked statically and i not linked glew32.lib or glew32s.lib

Title: Re: GLEW warnings
Post by: eXpl0it3r on May 12, 2014, 06:16:10 pm

• Get the latest SFML version from GitHub.
• Build SFML statically.
• Link SFML and SFML's dependencies (https://github.com/SFML/SFML/wiki/FAQ#wiki-build-link-static).
• Since SFML depends on GLEW, you'll have already linked against it.

Also define GLEW_STATIC in the project file and not in the source file.