![]() ![]() The path to the SFML headers ( /include) to the Compiler search directories. ![]() ![]() In the project's "Build options", "Search directories" tab, add: Now we need to tell the compiler where to find the SFML headers (.hpp files), and the linker where to find the SFML libraries (.a files). If you want to get rid of theĬonsole, in the project properties, go to the "Build targets" tab and select "GUI application" in the combo box instead of "Console application". Don't use it! It hasn't been updated in a long time and is likely incompatible with recent versions of SFML. Code::Blocks offers a wide variety of project types, including an 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 MinGW is not recommended, it's better You can then unpack the SFML archive wherever you like. If you feel like your version of GCC can't work with the precompiled SFML libraries, don't hesitate toīuild SFML yourself, it's not complicated. If MinGW was installed along with Code::Blocks, The libgcc_s_sjlj-1.dll or libgcc_s_dw2-1.dll files is present in your MinGW/bin folder. Make sure you select the package which corresponds to the version that you use. There are multiple variants of GCC for Windows, which are incompatible with each other (different exception management, It will explain how to configure your SFML projects.į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 Code::Blocks IDE, and the GCC compiler SFML and Code::Blocks (MinGW) Introduction ![]()
0 Comments
Leave a Reply. |