Welcome, Guest. Please login or register. Did you miss your activation email?

Author Topic: 65+ Warnings  (Read 5489 times)

0 Members and 1 Guest are viewing this topic.

e_barroga

  • Jr. Member
  • **
  • Posts: 76
    • View Profile
65+ Warnings
« 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.

Laurent

  • Administrator
  • Hero Member
  • *****
  • Posts: 32504
    • View Profile
    • SFML's website
    • Email
65+ Warnings
« Reply #1 on: July 17, 2009, 04:59:31 pm »
This means that the linker cannot find the debugging symbols for the SFML libraries.
Laurent Gomila - SFML developer

Mr. X

  • Jr. Member
  • **
  • Posts: 80
    • View Profile
65+ Warnings
« Reply #2 on: July 17, 2009, 08:46:00 pm »
I've got the same problem since I use SFML 1.5, but i ignored it until now...

e_barroga

  • Jr. Member
  • **
  • Posts: 76
    • View Profile
65+ Warnings
« Reply #3 on: July 21, 2009, 02:45:56 am »
Quote from: "Laurent"
This means that the linker cannot find the debugging symbols for the SFML libraries.


What am I supposed to do about it?

klusark

  • Newbie
  • *
  • Posts: 45
    • View Profile
65+ Warnings
« Reply #4 on: July 21, 2009, 02:48:05 am »
Refer to the tutorials getting started section. It will tell you what to do.

e_barroga

  • Jr. Member
  • **
  • Posts: 76
    • View Profile
65+ Warnings
« Reply #5 on: July 21, 2009, 03:07:37 am »
Quote from: "klusark"
Refer to the tutorials getting started section. It will tell you what to do.


If you're referring to this:
Quote

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.

klusark

  • Newbie
  • *
  • Posts: 45
    • View Profile
65+ Warnings
« Reply #6 on: July 21, 2009, 03:09:28 am »
You still need to link against the static libraries. For example sfml-system-s.lib.

e_barroga

  • Jr. Member
  • **
  • Posts: 76
    • View Profile
65+ Warnings
« Reply #7 on: July 21, 2009, 03:11:50 am »
Quote from: "klusark"
You still need to link against the static libraries. For example sfml-system-s.lib.


This is what I've got:
Quote

sfml-graphics-s-d.lib
sfml-window-s-d.lib
sfml-system-s-d.lib

klusark

  • Newbie
  • *
  • Posts: 45
    • View Profile
65+ Warnings
« Reply #8 on: July 21, 2009, 03:13:09 am »
Are the .pdb files in the same folder as the lib's? Did you build sfml your self?

e_barroga

  • Jr. Member
  • **
  • Posts: 76
    • View Profile
65+ Warnings
« Reply #9 on: July 21, 2009, 03:14:05 am »
Quote from: "klusark"
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.

klusark

  • Newbie
  • *
  • Posts: 45
    • View Profile
65+ Warnings
« Reply #10 on: July 21, 2009, 03:17:29 am »
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.

Laurent

  • Administrator
  • Hero Member
  • *****
  • Posts: 32504
    • View Profile
    • SFML's website
    • Email
65+ Warnings
« Reply #11 on: July 21, 2009, 08:40:36 am »
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.
Laurent Gomila - SFML developer

Alpha Nox

  • Newbie
  • *
  • Posts: 1
    • View Profile
65+ Warnings
« Reply #12 on: August 09, 2009, 12:46:15 am »
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. =)

LGV

  • Newbie
  • *
  • Posts: 11
    • MSN Messenger - laureano_river@hotmail.com
    • View Profile
65+ Warnings
« Reply #13 on: August 14, 2009, 04:42:50 am »
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:
Code: [Select]

#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

 

anything