VS 2017 Static & Dynamic problems with 2.4.2

[AshleyF]

Dear All,

I am having major problems with VS Community 2017 and 2.4.2 32-bit.

I follow the installation instructions to the letter, but it just will not work.

I've used CMake on the 32-bit source code, but that also doesn't work.

Does anyone happen to have any idea when a VSC 2017 specific stable release will be available please?

Kind regards,

AshleyF

[eXpl0it3r]

SFML works fine with Visual Studio 2017.

If you don't manage to create working builds on your own, I would in a first step recommend you try until you understand the error and manage to build SFML. It might be frustrating and time consuming, but learning you basic programming tools is simply a must.
If you're under time pressure, you can always grab my "nightly" builds.

Also "doesn't work" is not a problem description. If you want help with your problem, you first need to describe it properly. Thinking about the problem also often leads to understanding it better and maybe solve it on your own.

[Wafthrudnir]

I am using the latest SFML source and build it with Visual Studio 2017 and everything works fine. I once had a problem with msbuild because I had VS 2013 professional and VS 2017 community installed. I uninstalled everything but nothing worked...I resetted my windows 10 and reinstalled 2017. Problem solved (I work daily with VS and the way it's installed on a machine is just annoying).

What problem do you exactly have? What does CMake say? Or visual studio?!

[AshleyF]

Dear eXpl0it3r,

Thank you very much for your reply.

After downloading your nightly build and repeating the installation, I have discovered that:

1) The dynamic configuration works absolutely fine; but

2) The static configuration does not compile.

I have used both the 'lib' and 'static-std' in the project configuration setup and always receive the following compiler error message, this being the first one, with many others along the same lines:

LNK2019 unresolved external symbol __imp__wglShareLists@8 referenced in function "private void __thiscall sf::private::WglContext::createContext(class sf::private::WglContext *)" (?createContext@WglContext@priv...

and so the error message continues.

Any suggestions to overcome this problem would be most gratefully received.

Kind regards,

AshleyF

[Arcade]

Starting from SFML 2.2, when static linking, you will have to link all of SFML's dependencies to your project as well. This means that if you are linking sfml-window-s.lib or sfml-window-s-d.lib for example, you will also have to link opengl32.lib, winmm.lib and gdi32.lib.

Did you do this step, as described in the SFML tutorials?

[JayhawkZombie]

Are you linking all the libs?
I'm using the same version of visual studio as you, and I have these linked:

• sfml-graphics-s-d.lib
• sfml-window-s-d.lib
• sfml-audio-s-d.lib
• sfml-system-s-d.lib
• flac.lib
• freetype.lib
• jpeg.lib
• ogg.lib
• openal32.lib
• vorbis.lib
• vorbisenc.lib
• vorbisfile.lib
• opengl32.lib
• winmm.lib
• sfml-main-d.lib

(someone already mentioned the need to link all the dependencies as well before I finished this)

[AshleyF]

Dear JayhawkZombie,

Thanks very much for your reply.

Other than opengl32.lib, winmm.lib and gdi32.lib, all of the other libs are present.

After searching the hard drive and finding that they are not present, I googled for an answer.

It appeared to be the case that I'd need to install the latest Windows SDK.

I did that, and those libs still are not present anywhere.

Any advice would be most gratefully received.

Kind regards,

AshleyF

[eXpl0it3r]

You don't need to "find" them on your harddisk. You just need to link them. Those are system libraries and your compiler will find them on its own.

[AshleyF]

Dear All,

After reconfiguring the preferences in accordance with the advice given, I have discovered that:

1) A release build can compile, link and execute; but

2) A debug build cannot compile due to linker errors.

The error messages start with:

LNK2038 mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in main.obj

Any advice will be most gratefully received!

Kind regards,

AshleyF

[JayhawkZombie]

Try manually defining _ITERATOR_DEBUG_LEVEL.

Project > Properties > Configuration Properties > C/C++ > Preprocessor

and add '_ITERATOR_DEBUG_LEVEL=0' to the 'Preprocessor Definitions' section.  Microsoft has more info here about the macro https://docs.microsoft.com/en-us/cpp/standard-library/iterator-debug-level

[AshleyF]

Dear JayhawkZombie,

Thanks for the suggestion.

Although the linker error count has now come down to 33-ish, the new error being reported is:

LNK2038   mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MDd_DynamicDebug' in main.obj

Any suggestions would be most gratefully received.

Kind regards,

AshleyF

[eXpl0it3r]

The other suggestions for the iterator is not a fix for the root cause, but hack to make some symptoms go away.

You're either either linking the release SFML libs in debug mode or you've set the runtime lib to MD instead of MDd for your debug settings.

[AshleyF]

Dear eXpl0it3r,

From the VSC 2017 SFML build I downloaded that you made, there are two folders containing the relevant files.

I've tried each folder under both build options and still get the same error.

Any suggestions would be most gratefully received.

Kind regards,

AshleyF

[eXpl0it3r]

It's your project settings, as I already said.

You're either either linking the release SFML libs in debug mode or you've set the runtime lib to MD instead of MDd for your debug settings.

[AshleyF]

Dear eXpl0it3r,

Thanks very much for you reply.

Unfortunately, after trying everything you suggested, and checking and verifying everything you specified, it still isn't working

Any advice would be most gratefully received.

Kind regards,

AshleyF