SFML 2.0 Debug libraries in Code::Blocks

[Plaid Phantom]

Hi, I think I'm missing something.  I recently downloaded SFML 2.0 and ran CMake and compiled the SFML libraries, but I'm confused as to how I should go about generating debug libraries.  There's no option in the "Build Target:" menu for "Debug" as there was in 1.6 (IIRC; it's been a while since I compiled 1.6).  Is there something I need to do to generate debug libraries?

[eXpl0it3r]

You just need to set CMAKE_BUILD_TYPE from Release to Debug and then compile everything again.
Also you should always say which compiler you're using.

[Plaid Phantom]

Ah, thanks. I knew it would be something simple like that. I thought I had said I was using Code::Blocks (w/MinGW), but I guess I didn't. Thanks!

[eXpl0it3r]

I thought I had said I was using Code::Blocks (w/MinGW), but I guess I didn't.

I just now saw again that you specified Code::Blocks in the title, which usually implies MinGW, but it's also not always the case, so it's better to specify the actual compiler instead of just the IDE.

Also if you had read the official tutorial you'd have already had that information...

[Laurent]

I just now saw again that you specified Code::Blocks in the title, which usually implies MinGW, but it's also not always the case, so it's better to specify the actual compiler instead of just the IDE.

We don't really care about the compiler here, it's just a CMake and/or IDE issue.

Also if you had read the official tutorial you'd have already had that information...

In fact, CMake is able to generate multi-configuration projects for IDEs that support it. Code::Blocks does (like almost any IDE), so I'm surprised CMake didn't do it.

[Plaid Phantom]

Also if you had read the official tutorial you'd have already had that information...

I read it...at some point... 

Note that if you generate a workspace for an IDE that supports multiple configurations, such as Visual Studio, [CMAKE_BUILD_TYPE] is ignored and you automatically get all the available build types in it.

Yeah, this makes it sound like CMake should just provide "Debug" as a build target in my Code::Blocks project.  Is it working for anyone else?  I'll try to play with it over the weekend.

[Laurent]

In fact (after Googling a bit), the Code::Blocks generator of CMake is makefile-based, which means that it can't handle multi-configuration projects although Code::Blocks supports that.

The only multi-configuration generators in CMake are Visual Studio and XCode.

So yes, you must run CMake once for each configuration. But don't use Code::Blocks, since it's just for compiling SFML (not editing its source code), direct MinGW makefiles are simpler and more efficient, don't bother with an IDE.

[Plaid Phantom]

That all still seems weird, since as I understand it make (at least, linux make) does support targets, i.e. "make install", "make debug", "make clean".  But at this point it's a problem for CMake.  Thanks for the help!

[Laurent]

Targets are used for real targets, not for configurations. Don't forget that you can have several libraries / executables inside a single CMake project. So for example, for SFML the targets will be sfml-system, sfml-window, sfml-audio, ..., sfml-opengl, sfml-pong, sfml-shaders, ..., sfml-doc. Not "debug" and "release".

This is also explained in the CMake tutorial.