Code Blocks

Jetsonhacks himself has been kind enough to let a fellow jetsonhacker have a hand at adding some blog posts…so here goes.  I’ll just do a real quick intro of myself: My name is Neil, and I like the Jetson.  Good enough?  Okay, let’s move on to the topic at hand: Using Code::Blocks on the Jetson.

So, if you’ve never heard of code::blocks, it is an open source IDE.  It’s not the best IDE in the world, but it’s not the worst either.  I’d put it pretty close to the middle of the pack as far as functionality…but what it lacks in features, it makes up for in price: $FREE.  That’s a hard price to beat.

The reason I wanted to do a post about Code::Blocks on the Jetson is that for a while, I was coding on the Jetson without an IDE, and that got old.  I wanted the ability to step through code and group files together in projects.  Though Makefiles can do part of this, and gdb has some GUI front-ends (like DDD which is horrendous), I decided to try code::blocks owing to its freeness.

So, this post is about using Code::Blocks to replace an existing Makefile project and to provide the basic abilities of putting breakpoints in your code and debugging on the Jetson.  We won’t do any cross-compiling…everything will be done on the Jetson itself (easier that way, ain’t it?).