And again whether you choose to link dynamically or statically is really up to you and the project you are working on but for small projects I would suggest linking statically. Next you will need to add SFML_STATIC to your preprocessor options on both the release and debug build.Īfter that you are good to go and don't need to include the. lib files in VS's input window (Remember that -d is for the debug build). What you will need to do is recompile SFML's sources and make sure to build the library so it produces the static library files (They should be named something like sfml-graphics-s-d.lib for debug and sfml-graphics-s-d.lib for release).Īdd that library directory which contains the static library files to your project and then link to them. When you link statically you don't need to include any. exe file).Īnother option is to link statically instead of dynamically which I generally prefer to do on small projects but it is really up to the developer which he prefers. So youll most likely want to target 32-bit platforms, to have the largest possible audience. Indeed, you can perfectly compile and run a 32-bit program on a 64-bit Windows.
dlls that you are using into the same folder where your program's compiled executable is (The. On Windows, choosing 32 or 64-bit libraries should be based on which platform you want to compile for, not which OS you have.
dlls in different spots but since you are dealing with VS2013 you need to copy whatever. Now different IDE's require that you place the. The only directories you need to add to the project are the include directory and the library directory.īut anyways I am assuming you are using dynamic linking since otherwise you wouldn't be dealing with. You haven't given really to much information so I am just really guessing as to what the problem is.īut that sounds like your problem right there.
0 kommentar(er)
