Problem with MSVCP140d.dll

[Ezert]

Hello everybody.

Well. I installed SFML in Visual Studio with Static Link.
When I compile and run SFML programs on my computer, everything works.
The problem happens when I send my program to other computers and try to execute it: a missing "MSVCP140D.dll" warning appears...

Someone could help me?

I use Visual Studio 2017 and SFML 2.5.1

[Hapax]

I believe that to be the Visual Studio C++ runtime. It's the core C++ code and is needed to run any Visual Studio program.
To be clear, I presume you are statically linking SFML. You can, also, however, statically link the C++ core runtime. This is separate from statically linking SFML although you should also build SFML with the correct flag for doing so.

[fallahn]

I'll also note that msvc140d.dll is the debug version (there's a d on the end). You can't redistribute these, you need to rebuild in release mode before putting it on your other computer. Then installing vc_redist.exe from the Microsoft website on your other computer should fix your problem.

[Ezert]

Firstly, thank you two for help.

I'll also note that msvc140d.dll is the debug version (there's a d on the end). You can't redistribute these, you need to rebuild in release mode before putting it on your other computer. Then installing vc_redist.exe from the Microsoft website on your other computer should fix your problem.

I need to install vc_reddist.exe in every computer I send my program? :/
I chose to static link SFML to make my program simple...
There is no other way to fix it?

I believe that to be the Visual Studio C++ runtime. It's the core C++ code and is needed to run any Visual Studio program.
To be clear, I presume you are statically linking SFML. You can, also, however, statically link the C++ core runtime. This is separate from statically linking SFML although you should also build SFML with the correct flag for doing so.

I tried to statically link C++ as you told me, but now, for some reason, the building doesn't work! A lot of linking errors appears...
This is the tutorial I followed to static link C++: https://linustechtips.com/main/topic/622425-how-to-configure-static-linking-in-visual-studio/
What could I do next?

[Hapax]

If you statically link the core/standard C++ libraries then SFML needs to be built with that in mind so you will need to build SFML yourself.
In CMake, you probably want the SFML_USE_STATIC_STD_LIBS option.

This boolean option [(SFML_USE_STATIC_STD_LIBS)] selects the type of the C/C++ runtime library which is linked to SFML.
TRUE statically links the standard libraries, which means that SFML is self-contained and doesn't depend on the compiler's specific DLLs.
FALSE (the default) dynamically links the standard libraries, which means that SFML depends on the compiler's DLLs (msvcrxx.dll/msvcpxx.dll for Visual C++, libgcc_s_xxx-1.dll/libstdc++-6.dll for GCC). Be careful when setting this. The setting must match your own project's setting or else your application may fail to run.
This option should not be enabled simultaneously with BUILD_SHARED_LIBS, they are mutually exclusive.

[Ezert]

If you statically link the core/standard C++ libraries then SFML needs to be built with that in mind so you will need to build SFML yourself.

Ok. I'll try it.
But let me know something: everybody needs to do it, or it is specific for my computer?

[Hapax]

As far as I'm aware, it's not that common for SFML users to statically link the Visual Studio runtime.

People tend to be fine with distributing DLLs and the like. You should be aware that there are AAA games that first require you to have the Visual Studio runtime installed.