Skip to content

Latest commit

 

History

History
76 lines (54 loc) · 3.44 KB

README.md

File metadata and controls

76 lines (54 loc) · 3.44 KB

The Orocos Toolchain

The Open RObot COntrol Software (Orocos) Toolchain is a bundle of multiple packages, which need to be build and installed separately.

Futhermore the Orocos Toolchain comes with oroGen and some of its dependencies, a specification language and code generator for the Orocos Realtime Toolkit. Also check the installation instructions of the Rock - the Robot Construction Kit project for further details.

You might also want to have a look at the following sister projects, which are out of the scope of this manual:

Documentation

The latest documentation and API reference is currently available at https://orocos-toolchain.github.io/.

Get Started?

Install binary packages

The Orocos project provides binary packages as part of the ROS distribution for various platforms. Check and follow the ROS installation instructions, then run

sudo apt-get install ros-${ROS_DISTRO}-orocos-toolchain

to install the Orocos Toolchain packages.

As a ROS user, you might also be interested in the rtt_ros_integration project:

sudo apt-get install ros-${ROS_DISTRO}-rtt-ros-integration

Build the toolchain from source

First, clone this repository and its submodules with the command

git clone https://github.com/orocos-toolchain/orocos_toolchain.git --recursive

If you already have a working copy, make sure that all submodules are up-to-date:

git submodule update --init --recursive

The next step is to configure the toolchain according to your needs:

./configure --prefix=<installation prefix> [<options>]
Usage: ./configure [<options>] [<additional cmake arguments>]

Available options:

  --prefix <prefix>        Installation prefix (-DCMAKE_INSTALL_PREFIX)

  --{en|dis}able-corba     Enable/Disable CORBA transport plugin (-DENABLE_CORBA)
  --omniorb                Select CORBA implementation OmniORB
  --tao                    Select CORBA implementation TAO

configure is nothing else than a simple wrapper around CMake. Check ./configure --help for the latest available options.

Last but not least, build the toolchain by running

make install [-j<parallel jobs>]