But yes the lowest number of DLLs can be achieved by linking SFML static with static runtime lib and then everything static for your application.
I don't think you got my question right
Thats not what I wanted to achive, I knew that already about the static linking, its the process I currently use. I asked about the posibility to link the SFML library dynamically.
A: right now
Application.exe
libsndfile-1.dll
openal32.dll
B: wanted
Application.exe
libsndfile-1.dll
openal32.dll
sfml-audio-2.dll
sfml-network-2.dll
sfml-system-2.dll
sfml-window-2.dll
sfml-graphics-2.dll
C: only possible solution
Application.exe
libsndfile-1.dll
openal32.dll
sfml-audio-2.dll
sfml-network-2.dll
sfml-system-2.dll
sfml-window-2.dll
sfml-graphics-2.dll
libgcc_s_sjlj-1.dll
libstdc++-6.dll
+ legal attachments to gcc and stdc++
My question was about the possibility of solution B: distributing SFML DLLs without libgcc/stdc++ dlls and their legal attachments.