Code::Blocks

[bluntz]

Does anyone Have experiance with this IDE?

[MH]

On Windows I use both Code::Blocks and Visual C++ 2008 Express. Code::Blocks is fine; it's quite capable but does have a few annoyances (the lack of a Window menu is the biggest usability minus for me as it slows me down a lot when switching between open files - which I tend to do quite a bit of). The debugger in Visual C++ is vastly superior so that's my primary workhorse.

I do the occasional compile on Linux too and definitely prefer using an IDE to the terminal (I did command-line compiling and debugging in 1988 and they sucked then, it's 2010 now); Code::Blocks is weapon of choice there, mostly for reasons of consistency and familiarity than anything else.

[bluntz]

I am trying to compile the qrack 1601 source.
But its compiler is erroring on the commented out description lines.
This same source compiles cleanly outside the IDE
any insight would be welcome.

[email protected]:~$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-4ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
[email protected]:~$

This is the compiler outside IDE

[MH]

CB can be configured to use the same gcc as you're using in the terminal; something like Settings | Compiler & Debugger | Toolchain Executables is what you want.

[bluntz]

Thanks MH
I almost have it setup ok now.
The only issue left seems to be it seems to be using the -werror
switch treating warnings as errors even though my gcc was built with
-disable-werror
I am wondering does it have its own seperate gcc bin?
I found a compiler plugin enabled and have disabled it
Hopefully this will fix it and I can move on to updating
Any chance you have used Meld for patching C files?

[bluntz]

code::blocks has been updated from 8.02 to 10.05
for testing in lucid lynx

[mankrip]

Code::Blocks is fine; it's quite capable but does have a few annoyances (the lack of a Window menu is the biggest usability minus for me as it slows me down a lot when switching between open files

Go to "Settings -> Environment -> Notebooks appearance" and enable "Use Smart Tab-switching scheme" to enable a ctrl+tab switcher that also displays a list of the open tabs.

There's also the "Use drop-down tab list" option.

[MH]

Go to "Settings -> Environment -> Notebooks appearance" and enable "Use Smart Tab-switching scheme" to enable a ctrl+tab switcher that also displays a list of the open tabs.

There's also the "Use drop-down tab list" option.

It's a little better; not quite the same as Alt-w-1, etc, so there's some muscle memory that needs to be retrained, but a definite improvement on the default.

Any chance you have used Meld for patching C files?

We're well outside the territory of what I'm familiar with now, I'm afraid.

[bluntz]

Meld is a nice GUI for DIFF

Meld : Home Page