#1 Members - Reputation: 772
Posted 15 May 2012 - 12:15 PM
#2 Members - Reputation: 1830
Posted 15 May 2012 - 12:56 PM
If you don't like dynamically linking against Mingw's libgcc, you can always rebuild SFML with the SFML_USE_STATIC_STD_LIBS option set. This will statically link against the standard libraries, and prevent you having to ship libgcc_s_sjlj-1.dll or libgcc_s_dw2-1.dll with your application.
#3 Members - Reputation: 772
Posted 15 May 2012 - 01:05 PM
Well now it says that i'm missing libgcc_s_dw22-1.dll. >__> I do have libgcc_s_sjlj-1.dll in the bin directory now.Well, are you missing libgcc_s_sjlj-1.dll in your Mingw bin directory? Do you perhaps have libgcc_s_dw2-1.dll instead? I note that the download page for SFML includes links for versions linked against SJLJ and DW2, so it is possible you are trying the wrong package. As an example, I installed Mingw that came with Code::Blocks, and the variant of libgcc is provides is DW2, so any version of SFML linked against SJLJ won't work.
If you don't like dynamically linking against Mingw's libgcc, you can always rebuild SFML with the SFML_USE_STATIC_STD_LIBS option set. This will statically link against the standard libraries, and prevent you having to ship libgcc_s_sjlj-1.dll or libgcc_s_dw2-1.dll with your application.
The links for download for those versions are for 2.0 and i'm attempting to just use 1.6 for now. D:
#5 Members - Reputation: 163
Posted 17 May 2012 - 12:35 AM






