Visual Studio 2013 - Linking Problem

[Xornand]

Hello. I'm trying to build my project in Visual Studio 2013, however it throws linking errors, such as:

1>sfml-window-s.lib(WglContext.obj) : error LNK2001: unresolved external symbol __imp__wglMakeCurrent@8
1>sfml-window-s.lib(WglContext.obj) : error LNK2001: unresolved external symbol __imp__wglShareLists@8
1>sfml-window-s.lib(JoystickImpl.obj) : error LNK2001: unresolved external symbol __imp__joyGetPosEx@8
1>sfml-window-s.lib(JoystickImpl.obj) : error LNK2001: unresolved external symbol __imp__joyGetDevCapsW@12
1>sfml-system-s.lib(SleepImpl.obj) : error LNK2001: unresolved external symbol __imp__timeGetDevCaps@8
1>sfml-system-s.lib(SleepImpl.obj) : error LNK2001: unresolved external symbol __imp__timeBeginPeriod@4
1>sfml-system-s.lib(SleepImpl.obj) : error LNK2001: unresolved external symbol __imp__timeEndPeriod@4

And there's more.

I'm trying to link against the static libraries I built myself from the source code from the GitHub repository. Here's a short list of steps I followed:

• Downloaded the source code from https://github.com/SFML/SFML/archive/master.zip
• Unzipped files and built solution with CMake with BUILD_SHARED_LIBS flag being unchecked.
• Compiled both the debug and release versions.

And in my project:

• Copied all header (include) files to an appropriate folder.
• Copied all .lib files to an appropriate folder.
• Set my project to look for headers and .lib files in the appropriate folders.
• Defined all .lib include inputs, as following: sfml-main.lib, sfml-system-s.lib, sfml-window-s.lib, sfml-graphics-s.lib, sfml-audio-s.lib, sfml-network-s.lib for the release version and debug equivalent files (with the -d postfix) for the debug version.
• Added SFML_STATIC flag to preprocessor settings.

Am I missing something? A very similar setup worked fine on Visual Studio 2012 (with everything compiled under VC++ 11). I have no idea why it doesn't work here, any advice would be highly appreciated.

[Mario]

The wgl... functions should be in opengl32.lib. Did you forget linking it?

The other functions are inside winmm.lib.

If you're in doubt and think an unresolved external symbol should be provided by the Windows API, just look for "MSDN <function name>" on Google. It should point you to the correct MSDN page, e.g. timeGetDevCaps. Open the page and scroll down. It will list the header to use (which isn't important here) as well as the library to link to.

[eXpl0it3r]

Am I missing something? A very similar setup worked fine on Visual Studio 2012 (with everything compiled under VC++ 11). I have no idea why it doesn't work here, any advice would be highly appreciated.

You're using the latest version of SFML, thus you should be aware of changes that have happened to the source and thus tutorials might not be uptodate. A few weeks ago, SFML's way of linking dependencies for static libraries was changed. You'll now how to link the dependencies in your final application yourself.

More info an the full discussion can be found here.

[Xornand]

The wgl... functions should be in opengl32.lib. Did you forget linking it?

The other functions are inside winmm.lib.

If you're in doubt and think an unresolved external symbol should be provided by the Windows API, just look for "MSDN <function name>" on Google. It should point you to the correct MSDN page, e.g. timeGetDevCaps. Open the page and scroll down. It will list the header to use (which isn't important here) as well as the library to link to.

In fact I didn't link to those libraries. I assumed the static libraries would already contain all the dependencies. Especially the CMake options for linking dependencies were a bit misleading - it appeared to me as if everything would be included in the .lib files automatically. Anyway, thanks a lot for the info.

Am I missing something? A very similar setup worked fine on Visual Studio 2012 (with everything compiled under VC++ 11). I have no idea why it doesn't work here, any advice would be highly appreciated.

You're using the latest version of SFML, thus you should be aware of changes that have happened to the source and thus tutorials might not be uptodate. A few weeks ago, SFML's way of linking dependencies for static libraries was changed. You'll now how to link the dependencies in your final application yourself.

More info an the full discussion can be found here.

I wasn't aware of the changes. Thanks for the link.