MonoDevelop vs Code::Blocks a la Fedora 18

[Bryanstein]

I've been using MonoDevelop for programming in C++ because Code::Blocks has such pitiful support on Ubuntu, and I've managed to keep it through my switch to Fedora 18. Now I'm beginning to wonder if Code::Blocks is better than MonoDevelop on Fedora 18.

The problem I had with Code::Blocks: Inability to access the compiler (but I was told this was a problem with Ubuntu).
My problem with MonoDevelop: Lack of features for C++ programming (although this wouldn't be a problem if I wasn't forced to program in C++ because I would rather not).

If I should keep using MonoDevelop I'll want to know if there are any plugins to make C++ programming a but easier. If I go back to Code::Blocks I'll want to know if there's anything to make converting easier (importing things like color schemes and projects). Keep in mind that I'm programming for a class and technically I'm supposed to be using Visual Studio.

So, should I stick with MonoDevelop or should I try Code::Blocks again?

[ocratato]

Thanks for bringing Code::Blocks to my attention - it does look quite promising. However, I suspect I will stay with Eclipse for my large C++ projects since it is easier to get installed on work machines.

[Fenrin]

Codelite is also a nice, capable IDE. http://codelite.org/
It's not as mature as code::blocks yet, but very useable still.

main features are listed here. I tested it mainly, because I was interested in a IDE which supports Clang. Well actually it doesn't support it out-of-the-box, but I configured it to have also Clang as option (instead of gcc). I have not used it yet for any advanced C++ projects though.

[headkase]

If you go with Code::Blocks then make sure to use the version 12.11 rpms found on this page:

http://www.codeblocks.org/downloads/26

Fedora 18 is packaged with version 10.05 which is significantly older. Code::Blocks naming scheme is year.month so you can see that 12.11 offers much, much, more.