Hi, I'm a Linux user, so I will tell you how I expect to find things.
The following are only my opinions, it's not any rule.
The source tarball should only contains sources, no binary.
If you provide binary, the tarball should not contain any sources, but should tell where the sources can be found.
For building the sources don't use an exotic tool. Use something widely known and used.
Your build system should be configurable to find sfml in a non-standard location. Provide at least 2 variables to configure where to find SFML's include and SFML's .so libs. Tell in the README file how to use these 2 variables with an example.
If you provide a binary tarball, you may or may not also provide SFML's .so libs. If you don't tell where to download it. If you do write a "boot .sh" script that first set LD_LIRARY_PATH to the local path where the .so are, and then start your local ./program
LOCDIR=`dirname $0`
SFML_LIBS="${LOCDIR}/sfml_lib"
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$SFML_LIBS"
${LOCDIR}/program $*
If you don't provide sfml's .so, you can still provide this script, but tells in the README how to set the variable SFML_LIBS to the location of the sfml's so libs in case it is in a non-standard location.