Table of Contents

Overview

In order to generate executable binaries for the FESTO SBOx-smartcamera you need a Linux-PC1) to run the toolchain, but there should be no problem regarding the used Linux distribution. Already tested distributions:

For those developers just running Microsoft Windows® the only work-around by now are additional software tools like

Get the toolchain

You should have received a copy of the toolchain on your CD-ROM delivered with the camera.

Install the toolchain

create a new directory

Once you have successfully downloaded the toolchain package you are able to install it. Create a new directory /opt/sbo on your machine2). Alternatively you can install the toolchain to another directory of your choice and make a symbolic link /opt/sbo to your own installation directory.

copy the toolchain and extract it

Now copy the toolchain-package into the directory /opt and extract the content with the command line

tar xvjf toolchain-festo-gcc332-softfloat-1.3.tar.bz2
set environment variables

To work with your newly installed toolchain you will further have to set the path to your toolchain. The syntax for SuSE Linux is like:

/opt> export PATH=$PATH:/opt/sbo/gcc332/bin

For convenience, we recommend to set the path in one of your resource scripts on the development PC (e.g. .profile, .bash_rc, /etc/rc.local, …)

test the installation

The command-line

arm-linux-gcc --version

should print GCC 3.3.2

Install the camera related libraries

Copy the camera API libs into your toolchain or project directory. The location doesn't matter but be sure your compiler/linker can find them when you compile/link your programs for the camera. Each camera has it's API libs installed on the camera itself to avoid version conflicts between different firmware revisions. You will need the following files from your camera:

/lib/libcamera.a
/lib/libcamera.so
/include/OCamera.h

To get these files you can use either NFS, FTP or SFTP.

1) At the moment we do not support cross development under Microsoft Windows®
2) Usually you need root permissions to do so.