Carbide.C++ for standard C++ Win32 development

If you want to use Carbide.C++ for standard Windows development, here’s what you’ll need to do.

Window->Preferences->General->Capabilities->Advanced->Nokia Debug->Unused CDT UI

You should then find that all the standard CDT (C Development Toolkit) features become available.

Nokia has branched CDT in a few places, so not everything will work perfectly. However the only problem I’ve found is that I couldn’t immediately get GDB debugging to work with Nokia’s version of CDT. This is caused by Nokia’s branching but I’ve found a solution which I will write up at some point.

Meanwhile I’m quite impressed that Carbide isn’t a hacked-apart version of CDT; they’ve tried to extend it as politely as possible, so that none of the old functionality functionality is removed or disabled.

This entry was posted on Tuesday, January 2nd, 2007 at 3:22 pm and is filed under Techie. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

4 Responses to “Carbide.C++ for standard C++ Win32 development”

  1. macrobug Says:
    January 2nd, 2007 at 3:50 pm

    [...] As per my previous post, Carbide.C++ can be used for standard Win32 C++ development. This uses the facilities of the normal Eclipse C Development Toolkit (CDT) upon which Carbide.C++ is built. That, in turn, uses GCC for compilation, MinGW headers for Win32 API support, cygwin1.dll for UNIX API support, and GDB for debugging. [...]

  2. Adrian Taylor Says:
    January 2nd, 2007 at 3:51 pm

    The above link should take you to instructions showing how to get GDB debugging working.

  3. Adrian Taylor Says:
    February 14th, 2007 at 1:16 pm

    Doh! I spoke too soon. This doesn’t appear to work in Carbide.C++ 1.2 alpha.

  4. Adrian Taylor Says:
    February 14th, 2007 at 6:32 pm

    Aha – it turns out you need the Eclipse plugin org.eclipse.sdk for it to work. But then it works fine on Carbide 1.2 as well as 1.1.