The 2.0 release candidate.
So you copy the /lib and /include directories of SFML into your MinGW directory, and suddenly CMake finds FreeType... and is able to compile SFML?
Windows builds are self contained, all the external libraries required to build SFML are provided in the source package. It works out-of-the-box.
No. I copy them and the mingw g++ can compile the examples. Basically I took advantage of the windows build being self-contained so I could build the examples for windows.
Although cross compilation is a nice idea I can't really recommend it. It might work out of the box with some libraries/applications, but you can very easily waste hours of figuring things out, where as installing a VM and building native applications will take less time and can be reused.
Static linking SFML is really simple. Just link against the -s suffix libraries and define SFML_STATIC.
Also copying the libs into the MinGW dirs is not really recommended, you should rather specify at compilation, where to find the libs (i.e. set the -L flag).
See above post, using -s gives a host of undefined references (and yes I checked the -s and -d and -s-d libs do exis where I'm pointing -L at), so I must define SFML_STATIC, how do I go about that?