• Runtimes
  • Errors compiling with SFML.

Hello Mario,

I followed all the documentation tutorial for compiling SFML with your project, and I always have the same mistakes with SFML. Do you plan to update SFML support with the latest and released SFML 2.5.1 ? It won't work with the android stuff like LIBGDX as the SFML Team has stopped their work seen a long time. I need SFML/Spine working because I want to work on with the R.U.B.E. editor that works fine compiled with SFML 2.5.1. Thanks.

Related Discussions
...
  • Изменено

Hm, spine-sfml should work with SFML 2.5.1 without an issue. It seems that the SFML libraries are not linked to the example project in your case. Could you share the output of CMake when you create the Visual Studio solution? Did you modify the CMake files in any way, and if so how?

I've updated our spine-sfml example to use SFML 2.5.1 on the 4.0 and 4.1-beta branches of the spine-runtimes repository. I've tested it against MSVC 2017 and 2019, using the 32-bit x86 toolchain, as we use the 32-bit SFML prebuilt libraries. That worked as expected. Please pull the latest changes from spine-runtimes, clear your CMake cache, and regenerate your MSVC projects via CMake. Let me know if that still gives you issues.

Thanks a lot, Mario Nate, I will look inside the code. Hoping modeling physically based on projects runnig on a C++ library as I hope to port my future projects with Spine also under the Consoles C++. IUt's why I bought Spine PRO. So thanks for your help. Libgdx still stay the best for Andoid.


I was to fast happy. I 've corrected the error loadin jpeg.lib from the dependancies as it is not needed. The compiler stil have the same errors. there's an error to bild C code with C++ classes of SFML. Will it be correcte in the future ? Thanks.

Could you please post the error you are getting or alternatively provide your project e.g. via a GitHub repository? The spine-c, spine-cpp and spine-sfml runtimes compile fine on any compiler.

14 дней спустя

It works veryr well with x64 and x86. The origin was compiled with win32 under VS2017. I wrapped your code made it working with R.U.B.E and VS2022. All is Ok for me thanks for your advice Mario.