SFML community forums
Help => General => Topic started by: e_barroga on July 17, 2009, 04:52:25 pm
-
I am using VSC++ and I receive 65 warnings.
http://codepad.org/qUx4Epsk
My code has nothing more than a simple framework to initialize the window and clear and display.
I am also linking to static & debug libraries.
-
This means that the linker cannot find the debugging symbols for the SFML libraries.
-
I've got the same problem since I use SFML 1.5, but i ignored it until now...
-
This means that the linker cannot find the debugging symbols for the SFML libraries.
What am I supposed to do about it?
-
Refer to the tutorials (http://www.sfml-dev.org/tutorials/1.5/) getting started section. It will tell you what to do.
-
Refer to the tutorials (http://www.sfml-dev.org/tutorials/1.5/) getting started section. It will tell you what to do.
If you're referring to this:
Important: if you link against the dynamic libraries, you have to define the SFML_DYNAMIC macro in your project's settings. If you don't, you'll get linker errors when compiling your application.
I am not linking against dynamic libraries. I am using static.
-
You still need to link against the static libraries. For example sfml-system-s.lib.
-
You still need to link against the static libraries. For example sfml-system-s.lib.
This is what I've got:
sfml-graphics-s-d.lib
sfml-window-s-d.lib
sfml-system-s-d.lib
-
Are the .pdb files in the same folder as the lib's? Did you build sfml your self?
-
Are the .pdb files in the same folder as the lib's? Did you build it your self?
I haven't built anything. I am using SFML as I downloaded it.
-
The only way I know to resolve these warnings is to build sfml your self as the debugging symbols are not included in the prebuilt sdk.
-
It's weird because I didn't change anything, but there might be a bug in the last release with VC++ 2005 projects. I'll check this as soon as possible.
-
I just checked and the *.pdb files aren't included in the pre-built SDK.
Could you include them in the next releases? It's nice to have it already compiled for you. =)
-
Same trouble over here. The real weird thing it's that it start a few hours ago. Yesterday I've no troubles when compiling with the static debug libraries, but right now, I don't know why, it starts to do this weird thing. My code it's not the problem, if I just compile with the non-debug static libraries, it works fine. Maybe Visual Studio upgrades itself behind-the-scene and cause this kind of troubles (I would not be surprised with such thing coming from a Microsoft product...)? And it's extremely bizarre, I mean, I can't compile even this:
#include <SFML/Window.hpp>
int main(int argc, char* argv[])
{
sf::Window App(sf::VideoMode(800, 600, 32), "Testing SFML");
sf::Event Event;
while(App.IsOpened())
{
while(App.GetEvent(Event))
{
if(Event.Type == sf::Event::Closed) App.Close();
}
if(App.GetInput().IsKeyDown(sf::Key::Escape)) App.Close();
App.Display();
}
return EXIT_SUCCESS;
}
without getting the warnings (my additional dependencies are fine, they are: sfml-system-s-d.lib sfml-window-s-d.lib). So, this is very confusing for me, at the beginning I just think that I screw up something in my code, but now, well, I don't know...
P.S: this is my first post :D