Radarcape:ApplicationDevelopmentOnRC: Difference between revisions

From Beast Wiki
Jump to navigation Jump to search
imported>Dl4mea
Created page with "The Radarcape contains a full Linux system based on the Beaglebone hardware, so it can even be used for developing your own code. You can find plenty of information in the web..."
 
imported>Dl4mea
Line 1: Line 1:
The Radarcape contains a full Linux system based on the Beaglebone hardware, so it can even be used for developing your own code. You can find plenty of information in the web. Here, it shall only be showed how some small "hello world" and other small applications can be compiled and run on the Radarcape.
The Radarcape contains a full Linux system based on the Beaglebone hardware, so it can even be used for developing your own code. You can find plenty of information in the web. Here, it shall only be showed how some small "hello world" and other small applications can be compiled and run on the Radarcape.
__TOC__
{|
|[[File:Expert.png|For Experts]]
|''The tasks described in this manual require expert knowledge of Unix/Linux and embedded systems.''
|}


== Packages For C/C++ Development On Beaglebone ==
== Packages For C/C++ Development On Beaglebone ==

Revision as of 08:08, 7 October 2013

The Radarcape contains a full Linux system based on the Beaglebone hardware, so it can even be used for developing your own code. You can find plenty of information in the web. Here, it shall only be showed how some small "hello world" and other small applications can be compiled and run on the Radarcape.

For Experts The tasks described in this manual require expert knowledge of Unix/Linux and embedded systems.

Packages For C/C++ Development On Beaglebone

These packages are needed for C or C++ development on the Beaglebone:

opkg install update
opkg install gcc
opkg install gcc-symlinks
opkg install g++
opkg install g++-symlinks
opkg install make
opkg install boost
opkg install libc6-dev
opkg install binutils
opkg files libgcc-s-dev
 

It is recommended that these packages be updated in the explicit sequence above rather than all-at-once.