Static linking problem

[Sebox]

Hello

I try to static link my game and i get error.
I add SFML_STATIC to preprocessor.
In Release:

(click to show/hide)

sfml-window-s.lib
sfml-graphics-s.lib
sfml-audio-s.lib
sfml-network-s.lib
sfml-system-s.lib
sfml-main.lib
opengl32.lib
winmm.lib
gdi32.lib
freetype.lib
jpeg.lib
openal32.lib
flac.lib
vorbisenc.lib
vorbisfile.lib
vorbis.lib
ogg.lib
ws2_32.lib

In Debug:

(click to show/hide)

sfml-window-s-d.lib
sfml-graphics-s-d.lib
sfml-audio-s-d.lib
sfml-network-s-d.lib
sfml-system-s-d.lib
sfml-main-d.lib
opengl32.lib
winmm.lib
gdi32.lib
freetype.lib
jpeg.lib
openal32.lib
flac.lib
vorbisenc.lib
vorbisfile.lib
vorbis.lib
ogg.lib
ws2_32.lib

And when i run compile all is good but when i try to open my game i get error: "Program game.exe stopped working" when i use debug i get error in line when code is:

 RenderWindow window(VideoMode::getDesktopMode(), "Game", Style::Default, sett);

And the error is "Unhandled exception at the Location 0x77A2FF33 (Ntdll.dll)"
I use Visual Studio 2017, and i download package Visual C++ 14 (2015) - 32-bit
I really dont know where are problem.

[sjaustirni]

The compiler versions have to match 100%!

which basically means that you need to compile SFML on your own. thankfully, with VS 2017 it's easy these days.

• Just download the source code, open the folder in VS2017
• in the menu hit CMake->Generate cache (if it's not done automatically)
• Then right click on CMakeLists.txt -> Build -> All
• Check what is the folder where it has compiled and then just point VS with your own project opened to the right folder.
• Tadah, enjoy!

BTW, While we're at it, make sure that if you compile SFML for 32-bit, that you compile your project for 32-bit as well. The same goes for Debug/Release versions.

[Sebox]

Thank you for your answer, i add path for compile my own SFML(libs and include) and when i try co compile i get error

"LNK1104 cannot open file 'sfml-window-s-d.lib' client"

[sjaustirni]

This means that you point to a wrong folder, or that VS has no access to it. Check it.

Also, what compiler and linking chain do you use? The MSVC one, or CMake?

[Sebox]

I use CMake. I have 3 folders:


I use path to install:

include and lib. But in lib i only have:

so where can i should find files with suffix -s ??

[Laurent]

Look at the CMake tutorial, it explains all the options that you can change when you configure your SFML build -- including the one to build static libraries.

[Sebox]

Now i have error: "cannot open file freetype.lib"

[Laurent]

Where? When you do what?

[Sebox]

In compilator, when i try to compile program

[Laurent]

If you correctly installed SFML after building it, freetype.lib should be in the same directory as the SFML libraries. So I guess you haven't done the install step.

[Sebox]

I downloaded SFML source next i open this in CMake, next i choose when the CMake have to build the binaries and where is the source code, next i marked the SFML_USE_STATIC_STD_LIBS and i click Configure and Generate, next open the compiled of CMake in Visual Studio and click Build Solution in Debug and in Release.

After build solution i have this folder:


And i copy the libs from this folder /\ and include from SFML source to one folder. Next i set the path in visual studio to libs and include. But i dont have freetype.lib, only lib type "sfml-window-s.lib"

[eXpl0it3r]

If you build the INSTALL target (project) in Visual Studio you don't have to copy anything around.

[Laurent]

It is explained in the CMake tutorial, just read it (search "install" if you can't find where it is explained -- hint: it's at the end ).

[Sebox]

When i build INSTALL in visual studio i get error:

MSB3073 The command "setlocal
C:\Users\Sebastian\Desktop\cmake-3.8.0-rc2-win32-x86\bin\cmake.exe -DBUILD_TYPE=Debug -P cmake_install.cmake
if %errorlevel% neq 0 goto :cmEnd
:cmEnd
endlocal & call :cmErrorLevel %errorlevel% & goto :cmDone
:cmErrorLevel
exit /b %1
:cmDone
if %errorlevel% neq 0 goto :VCEnd
:VCEnd" exited with code 1.     INSTALL

[Laurent]

Is your CMAKE_INSTALL_PREFIX in C:\Program Files ? If so, you need admin rights (so I personally never install there).