Hello
I want to report I solved the problem.
I found a program called Dependency Walker
It is a fantastic program that shows in great detail what DLL's will be called by the program and how DLL's depend on each other.
https://dependencywalker.com/
Using this program I found out that I got burned (yet again) by the good old PATH variable in Windoze. The TGUI dll was calling a SFML dll that was in an earlier entry in the PATH. And that .dll happened to be a DW2 exception handler version. The error however, was pointing to libstdc++-6.dll BECAUSE the SFML dll was looking for the DW2 personality flag in the SJLJ libstdc++-6. Without dependency walker I probably would still be wondering whats wrong.
Fixed by putting the path to the SFML SJLJ directory before the path to the SFML DW2 directory ( I need both).
I want to report I solved the problem.
I found a program called Dependency Walker
It is a fantastic program that shows in great detail what DLL's will be called by the program and how DLL's depend on each other.
https://dependencywalker.com/
Using this program I found out that I got burned (yet again) by the good old PATH variable in Windoze. The TGUI dll was calling a SFML dll that was in an earlier entry in the PATH. And that .dll happened to be a DW2 exception handler version. The error however, was pointing to libstdc++-6.dll BECAUSE the SFML dll was looking for the DW2 personality flag in the SJLJ libstdc++-6. Without dependency walker I probably would still be wondering whats wrong.
Fixed by putting the path to the SFML SJLJ directory before the path to the SFML DW2 directory ( I need both).