Static library files for RelWithDebInfo configuration omitting '-s' suffix?

[hobby]

Building the RelWithDebInfo configuration of SFML statically using Visual Studio on a CMake-generated solution seems to produce lib filenames without the '-s' suffix. The Release configuration of the same solution does add this suffix. Is it intentional?

I used CMake 3.3.2 on the latest SFML repository with BUILD_SHARED_LIBS=FALSE and SFML_USE_STATIC_STD_LIBS=TRUE, and built with VS 2012.

[eXpl0it3r]

Looks like it for some reason never got added.

[hobby]

This is really a minor issue, I will just switch to the Release configuration. Thanks.

[eXpl0it3r]

I opened a PR for this: https://github.com/SFML/SFML/pull/1014

[Hiura]

I'm curious: is there any compatibility issue (I'm thinking release vs debug here) with this RelWithDebInfo mode on Windows?

[Rosme]

It's another mode. So RelWithDebInfo is incompatible with Release, and with Debug. But it can be useful to debug release.

[Jesper Juhl]

Just want to say, that including debug info in release builds is a really good thing to have working.
It doesn't cost you anything in runtime performance (although it costs a bit of disk space) but it can be invaluable when trying to debug a crash.
Debugging optimized code is *hard* but doing so without debug info is crazy hard.

[eXpl0it3r]

Well I wonder if it really works with SFML for VS, given that we don't even properly build nor package the debug info for debug builds for Visual Studio (related).

[Rosme]

I always forget that the PDB are not included. If the PDB were given(apart from the issue of generating them), I don't see why it wouldn't work.

[eXpl0it3r]

Problem being that CMake gives all the PDB files the same name and the absolute paths are embedded, i.e. making it pretty much useless to distribute.

Then again maybe there are some magic flags for CMake and VS. If so I'd like to know them.