SFML 2.0 in Linux

[santiaboy]

Hey guys, as 2.0 was released I wanted to try and code in Linux, too. I downloaded the file and then extracted it (because the sudo command brought me 1.6 )

However, when I try to do everything as the tutorial says, this happens:
 

||warning: libGLEW.so.1.7, needed by /home/santi/SFML-2.0/lib/libsfml-graphics.so, not found (try using -rpath or -rpath-link)|
/home/santi/SFML-2.0/lib/libsfml-graphics.so||undefined reference to `__glewUniform1fARB'|
//and 38 more errors

It happens when I try to compile via code::blocks, and via console, too! (It compiles, but the linker fails)

Aparently, I have a newer libGLEW, and that's why the error happens...so, any way to fix it? :p

EDIT: I don't know if it changes something, but I am using ubuntu 12.10

[fstream]

You could symlink your libGLEW.so to libGLEW.so.1.7 - it should probably work properly.

Better yet you can compile it yourself to make it link to the libraries you already have
http://www.sfml-dev.org/tutorials/2.0/compile-with-cmake.php

[santiaboy]

Shouldn't this be included in the tutorial? I mean, I followed it exactly as it said in the tutorial, and still couldn't get the program running...

Also, I could do that? Is there any other option? An easier one perhaps?

[eXpl0it3r]

It kinda depends, personally I feel like this is essentially an issue on the lack of knowledge on how Linux works and the error message is also quite verbose, so even if the Linux dev knowledge is missing, it should be fairly simple to google and figure it out.

The problem is, that SFML's Linux binary are linked against a specific version of GLEW (1.7) and if the linker can't find that specific version, it will complain. symlinking the libGLEW.so can trick the linker into thinking that it has the correct version, but it might not work correctly.
That whole problem should go away though, as soon as the official package managers will pickup SFML 2.0 as their new version, unfortunately this might take quite some time, depending on the Linux distribution.

And again as stated by fstream, the best way to go about any library, that isn't in the official packet manager, is to compile it from source. That's just kind how Linux is intended to be used.

[santiaboy]

...an issue on the lack of knowledge on how Linux works...

That might explain it, as I have little to none Linux knowledge. I guess I'll wait for the official packages, as I fear I will make a mess otherwise.

Thanks though!