SFML community forums
Help => General => Topic started by: Pixel_Outlaw on January 30, 2011, 12:17:06 am
-
Here is the error I am getting.
I've followed the tutorial but come up short with the following. I'm compiling it on Windows after using Ubuntu before. Do I need to build something? I know that in the tutorial there was mention of downloading a MinGW 4.4 file but the tutorial does not tell what to do with it.
http://img9.imageshack.us/img9/3066/helpsf.png
-
THis is not a sfml thing but a library in mingw. You just have to include the specified dll file in the same folder as the executable. You should find it in the bin folder in the mingw installation.
-
Thank you very much. It appears to be working as intended now. I've selected Code::Blocks because I want to make the finished code portable. :P
-
Good choice ^^
-
I just noticed that Code::Blocks has a feature to "create a new SFML Project". Is this a shorter way to configure everything? It asks for a SFML path during the creation process but I'm not sure what folder to give it. If I just give it the path to. This seems like an ideal solution if it works well. I would love to have the compiler set the proper directories at the start of a project.
My current try gave an error.
http://img266.imageshack.us/img266/5636/hmmmy.png
-
Never used it, but I think I saw someone else on the forum had a problem with it... Use the pretty search function :P
-
I've had nothing but trouble trying to set up the empty create new project things in C::B.
I ended up just setting up an sfml project and finding the "Save as a project template" (or something like that) in the File menu.
-
When you install the integrated version, it most likely puts the DLL in the "System32" folder. This is where the OS looks for DLL's. When you install the separate versions, the DLL may not get into your "System32" folder. Try looking through your MinGW and Code::Blocks files to find the DLL, then copy it to your "System32" folder. The path should look some like C:\WINDOWS\system32
___________________
Curtain Rods Hardware (http://curtainrodshardware.com)
[/url]
-
In Code::Blocks I use this linking options:
-static-libgcc
-static-libstdc++
to avoid libgcc_s_dw2-1.dll dependence. :)
This is the way to static link gcc libraries.