Page Personnelle de Vincent Kerhoas
Vincent Kerhoas
Professeur Agrégé
Page Personnelle de Vincent Kerhoas

Raspberry PI Cross Development Environment

Talking with the target

In following examples, static address for PC is
It can be modified with $ sudo ifconfig [Eth_name]


NOTE : ssh must be activated in raspi-config

Graphical mode :


Copy PC –> RPI

Copy PC <–> RPI


Host :
Username : pi
Password :
Port : 22

ssh/scp without password

RPI (via ssh)


Eduroam wifi Configuration

Compiling on Target

Considering the following helloworld.cpp file :


let’s copy it on the target :

RPI side (via SSH)

The RPI compiler is of course ARM type :

We compile, we execute :

Cross Compilation

Now let’s see how to create the RPI program on the PC.


An evidence : The PC has a compilation toolchain for Pentium.

ARM Linaro Compiler



It can be useful adding the linaro bin folder to the PATH :


PC Side

RPI Side (via SSH)

So this is exactly the same for a simple hello world.

with libraries ( ex : opencv )

It gets complicated ; let’s consider the opencv library.
The executable creation must be done with RPI opencv libs ( not the PC ones).

RPI Side

opencv installation

PC Side: RPI File system with sshfs

A solution could be copying RPI libs on the PC in order to create a minimal file system. This supposes dealing with dependances and update links to get relative paths.
An other solution, more elegant, is mounting the RPI file system through ssh thanks to sshfs.



This is the RPI file system ; it is mounted in PC rpi_mnt directory



let’s have à look to the Makefile:

Notes :

let’s go:

Test on Target

Debug with gdbserver

Ok we compiled, but how to debug our program ( other than with printf) ?

with tdb

you can get it in installations.html ( 1. IDE Eclipse / Tdb )

RPI side

PC side

In the project directory, create a .tdbinit file :

With Eclipse (Luna)

RPI side

PC side