Code::Blocks, free C++ IDE

Code::Blocks is a free C++ IDE built to meet the most demanding needs of its users. It is designed to be very extensible and fully configurable.

Finally, an IDE with all the features you need, having a consistent look, feel and operation across platforms.

Built around a plugin framework, Code::Blocks can be extended with plugins. Any kind of functionality can be added by installing/coding a plugin. For instance, compiling and debugging functionality is already provided by plugins!

Features

Highlights:

• Open Source! GPLv3, no hidden costs.
• Cross-platform. Runs on Linux, Mac, Windows (uses wxWidgets).
• Written in C++. No interpreted languages or proprietary libs needed.
• Extensible through plugins

Compiler:

• Multiple compiler support:
  
  • GCC (MingW / GNU GCC)
  • MSVC++
  • Digital Mars
  • Borland C++ 5.5
  • Open Watcom
  • ...and more
• Very fast custom build system (no makefiles needed)
• Support for parallel builds (utilizing your CPU's extra cores)
• Multi-target projects
• Workspaces to combine multiple projects
• Inter-project dependencies inside workspace
• Imports MSVC projects and workspaces (NOTE: assembly code not supported yet)
• Imports Dev-C++ projects

Debugger:

• Interfaces GNU GDB
• Also supports MS CDB (not fully featured)
• Full breakpoints support:
  • Code breakpoints
  • Data breakpoints (read, write and read/write)
  • Breakpoint conditions (break only when an expression is true)
  • Breakpoint ignore counts (break only after certain number of hits)
• Display local function symbols and arguments
• User-defined watches (support for watching user-defined types through scripting)
• Call stack
• Disassembly
• Custom memory dump
• Switch between threads
• View CPU registers

Interface:

• Syntax highlighting, customizable and extensible
• Code folding for C++ and XML files.
• Tabbed interface
• Code completion
• Class Browser
• Smart indent
• One-key swap between .h and .c/.cpp files
• Open files list for quick switching between files (optional)
• External customizable "Tools"
• To-do list management with different users

And many more features provided through plugins!


Get Code::Blocks.

Bloodshed Dev-C++

Bloodshed Dev-C++ is a full-featured Integrated Development Environment (IDE) for the C/C++ programming language. It uses Mingw port of GCC (GNU Compiler Collection) as it's compiler. Dev-C++ can also be used in combination with Cygwin or any other GCC based compiler.Features are :

- Support GCC-based compilers
- Integrated debugging (using GDB)
- Project Manager
- Customizable syntax highlighting editor
- Class Browser
- Code Completion
- Function listing
- Profiling support
- Quickly create Windows, console, static libraries and DLLs
- Support of templates for creating your own project types
- Makefile creation
- Edit and compile Resource files
- Tool Manager
- Print support
- Find and replace facilities
- CVS support

Visit Bloodshed Dev-C++ website here

Qt switch to LGPL

Hello all, I find a good article about the QT switch to LGPL . This is a copy:

Qt switch to LGPL has triggered a thread with subject "Bad thing for wxWidgets Qt will be in LGPL" on wx-users mailing list which clearly implies that this is indeed a bad thing. But is it one really?

First, let's not be egoistic: even if this were bad for wx, it's surely excellent news for just about everybody [else]. I do applaud Nokia for doing the right thing and I'm personally very glad that even people in big multinational companies such as Nokia understand the benefits of open source.

Second, this certainly will bring more users to Qt. But I'm not sure it's going to happen at the expense of wxWidgets users. I rather think more people thinking to use Java or C# or C (with GTK) could reconsider their choice and use C++ with Qt. The reason for this cautious optimism is that the cost of Qt has never been the only reason for choosing wxWidgets over it. Of course, this hasn't ever been important for GPL applications anyhow. And, surprisingly, it often wasn't very important for commercial applications neither as companies often choose to pay for wxWidgets support anyhow even if the library itself is free. So I think that relatively few of people who had chosen wxWidgets in the past would change their mind now, as the other two main reasons for this choice -- the use of native widgets by wxWidgets and the absence of any preprocessor -- remain as valid as ever.

Finally, if more people use C++ for developing cross-platform applications this is good for wxWidgets even if they use Qt because the whole idea of writing portable programs is unfortunately still not as entrenched in mass conscience as it should be in our opinion. So this could yet turn out to be positive for wxWidgets, although more likely it's not going to change much for us one way or the other.

But this remains great news for the open source community (of which we are part) so I just can't bring myself to regret it. I can dream about wxTNG which would combine the best features of wx and Qt but this still remains a dream for now...


Source : http://wxwidgets.blogspot.com/