Can't seem to install SFML

[greenleaf800073]

wait, what do you mean by save all? I checked the .zip that contained everything, and everything is there

I just tried to download my own file, it works .-.

[eXpl0it3r]

There's no purpose in attaching the same thing three times.

The project file you posted is an XML file (see above) and it has no information of the libraries, so either you didn't add them or you forgot to save the project file itself (doesn't happen with Ctrl+s). To guarantee the saving of the project file you can choose to "Save All".

[greenleaf800073]

Ok, I've clicked 'save all files'

[eXpl0it3r]

Well something changed, but nothing in the project file.
What happens if you close Code::Blocks and reload the project, because I've no idea why you say the settings are there even though they aren't in the project file.

[greenleaf800073]

Oh, it asked me to save .-. that's so weird, why can't I do that when inside the compiler, I think it added a .layout

[eXpl0it3r]

Maybe "Save all projects" would've done it as well, you know one needs to be flexible and innovative.

Anyways, now we get the settings...

#include "C:\Users\cocon_000\Desktop\SFML-2.1\include\SFML\Graphics.hpp"

Don't do that. You add the include directory to the compiler, thus the compiler knows where to look for the header if you do it like this:

#include <SFML/Graphics.hpp>

Also make sure whenever you change something in the linking settings to do a full rebuild.

[greenleaf800073]

Oh yea, I forgot to change that back to #include <SFML\Graphics.hpp>

It was originally that ^ but then it still didn't work, so then I changed it to #include "..."

[Nexus]

And use forward slashes for paths, they're portable.

#include <SFML/Graphics.hpp>

I don't even know why people came to the idea of using \ for #include. Not even the bad books teach that...

[greenleaf800073]

And use forward slashes for paths, they're portable.

#include <SFML/Graphics.hpp>

I don't even know why people came to the idea of using \ for #include. Not even the bad books teach that...

? \ are for computer paths, what are portable paths?

[eXpl0it3r]

Back-slashes are used by Windows (only) for paths. All Unix based systems (Linux, OS X, etc) use forward-slashes. C++ uses back-slashes as escape character (e.g. \n = new line, \t = tab, etc) and it understand forward-slashes for all kind of paths just fine, thus you should never use back-slashes for paths in C++.

"Portable" means that it can be used on any system.

[FRex]

And use forward slashes for paths, they're portable.

#include <SFML/Graphics.hpp>

I don't even know why people came to the idea of using \ for #include. Not even the bad books teach that...

That's the default for VS, at least 2010. There is an option to never use backslash too.
https://connect.microsoft.com/VisualStudio/feedback/details/499097/c-header-completion-should-use-forward-slashes-not-backslashes
http://support.wholetomato.com/default.asp?W337

[greenleaf800073]

oh ok, I get it now

well, can you guys help me though?

[eXpl0it3r]

All I got what I already said, because it works totally fine on my end.

Also make sure whenever you change something in the linking settings to do a full rebuild.

[greenleaf800073]

Should I have relative paths or direct paths?

[eXpl0it3r]

Well the question is for what exactly, but in the end it doesn't really matter.