Why did you choose Code::Blocks?

[SashaGT]

I've been using Code::Blocks for probably a decade by now. My first IDE, the one I felt confident using, was Dev-C++. Likely because it was an easy install. It definitely was the first tool I used to compile C++ code.. but sometime soon after I started compiling C++ programs using Code::Blocks. I don't know why or how I came to use it but for this reason I've signed up to the forum a decade later looking for answers.

Why did you download a start using Code::Blocks?

After reading through the forums I found that this might be a refreshing question of self-reflection and exploration; I truely am curious as I don't quiet exactly remember how I came about this wonderful IDE and am hoping to rediscover the reasons as to why I had decided to commit myself to Code::Blocks for the last 10 years.

All I know is that it's familiar and I keep coming back! 

[Miguel Gimenez]

I was using C++ Builder, but was disappointed with the incompatibilities and limitations of their compiler.

I tested Dev-Cpp for game developing on MSW, but it was mostly abandoned and I needed Linux support.

I then tried Anjuta, but had no support for MSW and I did not like it.

Finally (2009) I ended with C::B because Ubuntu software repository offered it, and there was a version for MSW with identical GUI.


Side note: I hate-hate-hate MS tools and MS-isms like ATL, #pragma once and other "features" created just for making difficult returning to GCC.

[SashaGT]

I understand the sentiment towards MS. I had a bad experience with an MSVS beta version that was preventing the latest non beta version from installing despite it being uninstalled. Looking back it was probably a Windows registry key problem.

I bet I was wanting to use the new C++ standards and I couldn't figure out how to replace them in Dev-Cpp back then.. so then I found C::B; a just as easy to install IDE with the latest MinGW compiler. I remember reading forums discussing C++0x and being very interested. So it's possible I migrated to C::B shortly after the release of C++11 once MinGW supported it.

Now that I've had a bit to sit and think about it that's probably what happened.

Thanks for sharing!

[Pecan]

I had clients who wanted to migrate to Linux, but my software was Windows only.

I found a team that was writing an IDE that supported both Linux and Windows named "Code::Blocks".

It was the shortest route to convert/support my software.
MSBuild console .bat system got retired for testing only. Never looked back.

[SashaGT]

Solid reason! I've always tried to write software that's as platform independent as possible. I had intended to compile some of my projects for Linux but haven't gotten around to it. I don't think I started using C::B because of it's Linux support but it's definitely something that I've been planning on taking advantage of more recently.

[nenin]

Why did you download a start using Code::Blocks?

70% the same as Miguel Gimenez.

1. I had to migrate to open source from Borland (many years ago).
1. Also I have to keep in mind multiplatform possibility.
1. For some time I used Dev-Cpp, but it was abandoned de-facto. Also it was underdeveloped.
1. There were some alternatives, but not good.
1. C::B was already operable with non-crucial issues. It also supported Fortran, which I need from time to time.

[cacb]

I come from a background where the company I worked for developed and delivered software for VAX/VMS and a number of Unix platforms. So cross platform was always my perspective. Then in the 1990s, Windows took over and development became more and more MSVS centric with GUIs using MFC, and cross platform kind of faded away, which I did not really enjoy.

I was looking for a good solution for cross platform GUI and found that wxWidgets was the best answer, it is native on all platforms which I think is the right approach. Code::Blocks supports wxWidgets development via the simply excellent and very important wxSmith plugin. wxSmith is a major reason for choosing Code::Blocks.

Also, Code::Blocks has its own build system that works the same on Windows and Linux (the platforms that matter to me). You can use GCC everywhere like most people do, or you can do what I do: Within one and the same project I have build targets for the MSVC compiler (used on Windows) and also for GCC (used for linux). This is as good as it gets for my use, the software is native everywhere and I can update the project files everywhere and use git to synchronize between platforms.

I have used Code::Blocks more or less this way since about 2008 and I enjoy it. I use the Nightly Builds of C::B on Windows and I build from source on Linux. I have a git mirror repository that is automatically updated every day from the SourceForge SVN original https://github.com/arnholm/codeblocks_sfmirror

Many thanks to the developers and maintainers of Code::Blocks!

[SashaGT]

Code::Blocks supports wxWidgets development via the simply excellent and very important wxSmith plugin.

Yes! I've not much experience with wxWidgets but I've known about it and the plugin for some time now. I really ought to invest some time into learning more about it. I typically create an empty project and link everything I need manually via the build options but I recognize there's quiet a few templates that exist packaged with C::B. I've seen the wxWidgets template a few times but haven't had the time to investigate it.

Oh, I've also been reminded (just today) via the C::B splash screen that it's open source... likely another reason I was drawn to it!

[speedreadersteve]

It's simple to pick up and start coding with, which is good for a beginner like me.  It also has enough power to it that I don't have to hop over to visual studio in order to create something like a project.

[Butter-Swimming Butterfly]

1. For Windows users, the other primary IDE option has been Visual C++ during the past couple decades. Visual C++ just had more annoyances during the last times I've tried it.
  ~ For example, Code::Block's debugging (GDB) graphical user interface is superior to what Visual C++ (and other C++ IDEs which are available for Windows users) offered last time I tried. VC++ had an inconvenient command-heavy interface if I remember right.
  ~ Visual C++'s solution/project configuration system was stupid (and it might still be).
  ~ Also, Code::Blocks was designed to work with GCC (and MinGW). MSVC doesn't really support the C++ standard as completely as GCC. GCC is a good compiler suite for C++ programmers.
2. Code::Blocks has a graphic style that is tightly-fitted, mostly uniform (non-messy spacing between layout content), and adequately colorful. I think it looks sharp, so I like it.

[Bug Killer]

I use Code::Blocks because of wxWidgets ;=)). I write open source software for railroad model management. I am keen to make them work with Windows and Linux.

[Grit Clef]

Then I'd like to say that CodeBlocks is the most powerful and smart IDE of all the C/C++ IDEs. Because it's small but has wonderful functionalities and the highest speed of all those IDEs which have a good UI, I choose it at last.

[ollydbg]

I use Code::Blocks because of wxWidgets ;=)). I write open source software for railroad model management. I am keen to make them work with Windows and Linux.

You image screen shot of the application looks nice, good work!

[ollydbg]

Back to the year around 2007, I was using Microsoft's MFC as a framework, and I found that I need a cross-platform GUI framework, and I finally choose wxWidgets. I was using Dev-Cpp IDE, but I soon found Code::Blocks is better, and I finally choose Code::Blocks.

Later, I see it had some bugs and some missing features, so I tried to contribute to C::B. I remembered that in that years, when I tried to start debugging C::B inside C::B, the gdb start time is about 1 minute or 2 minutes to load the debugee C::B.