Hi Bryan,

We are looking at the same thing at the moment - it's clear there's no easy way to programming the Raspberry Pi in C/C++ currently which is crazy.  We're hoping to crack this and then create some kind of example set-up people can download for free.

However we're not there yet so bear with us!

Cheers

Richard

Hitex UK

Richard Gledhill wrote:

it's clear there's no easy way to programming the Raspberry Pi in C/C++ currently which is crazy. 

If by easy you mean a gui dev environment, you are right, but all the dev tools are available on the pi for c, c++ programming. If they don't come with it they are certainly available via apt-get. And they are free. All my pi development consists of 3 or 4 terminal windows ssh'd into the pi. Just like my linux development on x86.

You kids today and your fancy GUIs

Mike

Wouldn't real men do it with punch tape...?

Mark

Wouldn't real men do it with punch tape...?

Mark

Mark Beckett wrote:

 

Wouldn't real men do it with punch tape...?

 

Mark

I've always thought of Unix as a very efficient way to process virtual decks of cards.  The whole stdin/stdout approach is like a card reader blasting in text and a card punch blasting out object code, with a teletype sitting on the side for stderr.

When I used CMS at IBM in the 1980s you actually used a virtual card reader to receive e-mail and a virtual card punch to send e-mail.  IBM still had a fondness for punched cards since they used to make a large part of their income manufacturing and selling them.

I once had a boss that told me the tales of doing development on their mainframe after the normal day finsihed.

They would have to load the new programme/configuration with punch tape, which wasn't quick.

The older guys at work remember (with some fondness ...) the AFTN system (think teletype) where it spat out on punch tape, and then got loaded into wherever it needed to go.

They could read the messages directly off the tape .....

I guess that was their gui.

We have come a long way in a short time...

mark

Mark Beckett wrote:

 

Wouldn't real men do it with punch tape...?

 

Mark

Real men do it with neons and switches. Sheesh, you kids and your fancy EMUI's*

Seriously, the Code Sourcery toolchain does the trick. Eclipse is designed to support cross compilers and remote debugging. I have configured it to do so for several devices. I have not so far had a reason to do so for the Pi but I'm sure it will be as straightforward as the others.

I have read that Eclipse can run directly on the Pi, but having run the Arduino IDE on the Pi I would suggest you don't even try Eclipse.

Derek

* Electro-Mechanical User Interface

Yes, you can do it with eclipse, but not with the toolchain producing the error messages above, that is clearly the arm-none-eabi, the one he will want to get is found here

http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/request?id=478dff82-62bc-44b2-afe2-4684d83b19b9&downloadlite=scblite2012&fmpath=/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/form

that is

Sourcery CodeBench Lite Edition for ARM GNU/Linux

as I said I have done it with eclipse on linux I assume the same is available for windows. Also

https://sourcery.mentor.com/sgpp/lite/arm/portal/kbentry34

tells why there are 3 different arm-*-eabi toolchains.

Mike

Also if you look at the error messgaes spit out above it compiled fine. The issue was in the linking. It couldn't find the libraries it needed to do the simple "printf()"

that he probably calls in his program.

Well, they say the pi is a tool for education, this guy will learn alot by getting eclipse for windows to compile an executable for the pi.

All good.

Mike

Mark Beckett wrote:

 

Wouldn't real men do it with punch tape...?

 

Mark

Yes

Honestly, I've never used punch tape professionally. During my training we had to punch a diagnostic routine and I learned how to fix a punch and reader, but I never had to use one IRL.

Mike

Bringing this back on topic (and back into the 21st century...) we've now cracked it!  We can now develop code on a PC in an Eclipse-based environment and then remotely debug it on the PC, with the application running on the Pi.  We can run to main(), single-step, watch variables, all that good stuff :-)

Top-secret how we did it for now but we'll be putting up a guide how to do it in the next few days...

Cheers

Richard

Hitex UK Ltd

Hi Richard,

  Nice to hear that. Hopefully we can include all kinds of libraries as well, include libc, opengl, libbcm, etc.

  Hope to hear to good news from you.

Cheers,

Bryan

HI Richard,

Great idea. Would we need anything else other than the GDB server on the RPI?

Right now, this is how I am developing my apps.

App compilation and debugging are being done onto the PC side. After compiling the app with debug symbols, I need to copy the PC cross-compiled executable onto the RPI and run it using the GDB server.

On the PC side, the GDB (coming with the cross-compile package) will connect to the RPI GDB server through ethernet. Afterwards, happy debugging.

Is this setup similar to what are you going to present in the guide?

Cheers,

Bogdan