depthBits is the number of bits per pixel to use for the depth buffer (0 to disable it).This argument is an instance of the sf::ContextSettings structure, it provides access to the following In case you think it is too automatic, sf::Window's constructor has an extra argument that allows you to change the settings Since SFML is based on OpenGL, its windows are ready for OpenGL calls without any extra effort. Remember this when you get linker errors, it will help you find which library you forgot to link. OpenGL functions start with the 'gl' prefix. Therefore, you need to know which library to link to according to what operating system you're using ('opengl32' on Windows, 'GL' on Linux, etc.). Unlike what it does with the headers, SFML can't provide a unified way of linking You will then need to link your program to the OpenGL library. From the user's point of view, OpenGL extension loading must be handled like any other external library. People sometimes think that SFML automatically includes OpenGL extension headers because SFML loadsĮxtensions itself, but it's an implementation detail. This header includes OpenGL functions, and nothing else. Therefore, SFML provides an 'abstract' header that takes care of including the right file for you. OpenGL headers are not the same on every OS. Including and linking OpenGL to your application

Let's see how it allows you to play with OpenGL. That's where the sfml-window module comes into play. You would have no choice but to write OS-specific code to handle this stuff on your own. But OpenGL alone won't be enough to create complete programs: you needĪ window, a rendering context, user input, etc. This tutorial is not about OpenGL itself, but rather how to use SFML as an environment for OpenGL, and how to mix them together.Īs you know, one of the most important features of OpenGL is portability. Using OpenGL in a SFML window Introduction

Get opengl 2.0