limker error when using sf::time operators

[okeidar]

Hello!
when i use a the operators of sf::time i get the following error

(click to show/hide)

Error   5   error LNK2019: unresolved external symbol "class sf::Time & __stdcall sf::operator+=(class sf::Time &,class sf::Time)" (??Ysf@@YGAAVTime@0@AAV10@V10@@Z) referenced in function "public: void __thiscall Game::Run(void)" (?Run@Game@@QAEXXZ)   C:\Users\Omer\Documents\Visual Studio 2010\Projects\SFML - FirstFullGame\Main\Game.obj   Main

now i have checked the linker settings and i do link it to sfml static libraries and define the precompiled header.
when i use sf::time methods other then the operators i get no messages

Thank you for reading

[Gambit]

Precompiled header? Do you mean the preprocessor SFML_STATIC define? Also which version of SFML are you using and on what OS? Try getting the latest version and/or compiling from source.

[okeidar]

Yes, I meant preprocessor SFML_STATIC, thank you.
i use sfml 2.1 on VS2010 on Windows 7.
I thought i might not have the most recent version so i downloaded the latest.

[okeidar]

OK i have changed the calling convention from _{__stdcall} to _{__cdecl}
and it fixed the errors.
can anyone explain how does it matters?

[wintertime]

If you set incompatible compiler options you want to get an error, because thats much better than silent corruption at runtime.

[okeidar]

yes i understand, but why does sf::time operators work with __cdecl and not with __stdcall?

[wintertime]

Because they were compiled that way. (You would need to recompile all libraries with the same setting to make them compatible, but thats much pain for a tiny or possibly even negative gain. You better dont waste time on such microoptimizations.)

[Laurent]

Well... there's no reason why a default SFML build wouldn't work with a standard Visual Studio 2010 project. And there's no reason why only sf::Time operators would trigger such a linker error.

I'd say there's something wrong in your environment, but it's hard to say what.

[okeidar]

Well... there's no reason why a default SFML build wouldn't work with a standard Visual Studio 2010 project. And there's no reason why only sf::Time operators would trigger such a linker error.

I'd say there's something wrong in your environment, but it's hard to say what.

well i  hope ot wont happen again
its wierd because i read that windows application should compile with __stdcall and that WINAPI is actually an __stdcall definition..

thanks everybody:)