You can run ‘make’ at the command prompt and it will create a program call testConsole that you can run and see the output. If you go into the folder you just cloned, you’ll see a Makefile that looks like the following: I have an example that I’ll use on github that uses ANSI codes to print stuff to a terminal and periodically clear the screen so that the screen updates in a nice fashion. Let’s take a look at a simple C++ project that currently uses a Makefile and convert it into a Code::Blocks project (.cbp file). You should also be able to install it through Ubuntu Software Center. I installed this a while ago, so hopefully I’m not forgetting any dependencies (if I did, let me know in the comments and I’ll add them). We won’t do any cross-compiling…everything will be done on the Jetson itself (easier that way, ain’t it?). 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. 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. I wanted the ability to step through code and group files together in projects.

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’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. It’s not the best IDE in the world, but it’s not the worst either. So, if you’ve never heard of code::blocks, it is an open source IDE. Good enough? Okay, let’s move on to the topic at hand: Using Code::Blocks on the Jetson.

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

Setup codeblocks compiler reddi