After building the examples, at least 2 things to be done for an example

[jronald]

Develop Environment:
    Visual Studio 2013
    Windows 7
    Debug

0. In project/property page/Debugging set Environment to ../../lib/Debug
1. copy the resource directory to the project directory if there is one

Why not to make it automatic?
Thanks.

[Gambit]

"After Build" settings are IDE specific, and especially if you arent using an IDE, this cannot work and instead CMake would have to generate platform specific post-compile scripts to do this for you.

In short: dont be lazy.

[jronald]

When it doesn't running, I have to find the problems, this is not so efficient, if the author can refine the CMake file, it'll be much more efficient for others.

[Gambit]

Such is the life of the programmer. You shouldnt have to rebuild SFML a whole lot and if you are, you probably dont have a good reason to be doing it. If you are having problems getting the examples to work, you are probably doing something wrong.

[jronald]

This is not very efficient, when the example doesn't run, it depends on the error messages from the development tools to solve the problem. Fortunately, the error messages helps here. Copying the resource directory is just a must-to-do, why not copy it automatically? Setting the path to find the dll or copying the dll into the exe directory or any other methods needs decisions. Fortunately these are for examples.

[Gambit]

I dont even know what you are getting at. At you complaining that you have to copy the dll for SFML modules into the same directory for each project?

[jronald]

Yes, all the misc things, it makes inefficiency.
However it is not a big problem for examples.

[Gambit]

Its not a problem for anyone with a well structured development environment actually. This "problem" isnt specific to SFML, its how it works for everything, especially on windows.

However, like with *Nix, you can just chuck your dlls into system32 and you dont have this problem anymore, but dont do that.

Its also worth noting that when you link statically, you also do not have this problem, you should consider doing that if this bothers you so much.

[eXpl0it3r]

If you do not have multiple SFML versions on your system, you could also have a directory with the DLLs and add them to PATH.
As Gambit says this is nothing specific to SFML, whenever you use a library you need to think about where to put it.

[jronald]

Its not a problem for anyone with a well structured development environment actually. This "problem" isnt specific to SFML, its how it works for everything, especially on windows.

However, like with *Nix, you can just chuck your dlls into system32 and you dont have this problem anymore, but dont do that.

Its also worth noting that when you link statically, you also do not have this problem, you should consider doing that if this bothers you so much.

But when I run cmake -P cmake_install.cmake, everything needed is copied, including resource directories and all the dlls.

[Gambit]

Ok? Then whats the issue?

[jronald]

The issue is that it has been done when installing, why not when generating the solution for vs2013?

[eXpl0it3r]

CMake is not a build tool, it only generates make and project files. You then have to build them in a next step on your own.

[jronald]

The resource directory is also a part of a project.

[eXpl0it3r]

Maybe you should ask a friend to help you translate your problem better, because we've no idea what you want to achieve...