These paths are the same in both Debug and Release configuration, so you can set them globally for your project ('All configurations'). The path to the SFML libraries ( /lib) to Linker » General » Additional Library Directories.The path to the SFML headers ( /include) to C/C++ » General » Additional Include Directories.Now we need to tell the compiler where to find the SFML headers (.hpp files), and the linker where to find the SFML libraries (.lib files).

(otherwise Visual Studio doesn't know which language you're going to use for this project). The dialog window offers a few other options to customize the project: select 'Console application' or 'WindowsĪpplication' only if you know how to use pre-compiled headers.įor the purpose of this tutorial, you should create a main.cpp file and add it to the project, so that we have access to the C++ settings It is recommended to select 'Empty Project'.

The first thing to do is choose what kind of project to create. To keep libraries in their own separate location, especially if you intend to use several versions of the same library, or several compilers. Copying headers and libraries to your installation of Visual Studio is not recommended, it's better You can then unpack the SFML archive wherever you like. If there's no SFML package compiled for your version of Visual C++, you will have to Won't be compatible with VC++ 12 (Visual Studio 2013) for example. Indeed, a library compiled with VC++ 10 (Visual Studio 2010) You must download the package that matches your version of Visual C++. It will explain howįirst, you must download the SFML SDK from the download page. This tutorial is the first one you should read if you're using SFML with the Visual Studio IDE (Visual C++ compiler).

Microsoft visual studio c++