This page explains how to install Rock and where to look for more information (tutorials, …)

Level of support

This section lists the operating systems where Rock is well tested, is untested and whose status is unknown. For well tested operating systems, a build server makes sure that Rock builds fine, and it is known to be actively used. Untested operating systems have had users (so, it did work at some point), but it is unknown whether it is still being actively used. Finally, unknown status operating systems are OSes where Rock should work, but we have had no known report of its success or failure.

Well tested Oses

	Since 10.04
	testing or unstable

Untested OSes

	Last known working version end of 2011
	Last known working version end of 2010

Status for other

Other Linux distributions	Should work fine. No osdeps.
Mac OSX	Known to have problems. No osdeps.

Installation: the easy way

1. Make sure that the Ruby interpreter is installed on your machine. Rock requires ruby 1.9.2 or higher, which on Debian and Ubuntu are provided by the ruby1.9.1 package.

   ruby –version

2. Create and “cd” into the directory in which you want to install the toolchain

3. To build the base system (base packages + toolchain, but no libraries/components), use this bootstrap.sh script. Save it in the folder you just created. For other options, see below.

   There is an important note for long-term Orocos users. See the red box below.

4. In a console, run

   sh bootstrap.sh

5. Important: as the build tool tells you, you must load the generated env.sh script at the end of the build !!!

   • source it in your current console

     . ./env.sh

   • but also add it to your .bashrc: append the following line at the end of $HOME/.bashrc

     . /path/to/the/directory/env.sh

6. read the autoproj guide for basic usage to know the basic operations of the build system. More bootstrapping documentation is also available at the same place

Other bootstrapping options

• to build all of Rock, use this bootstrap.sh instead of the one listed above. ‘'’This is really meant for continuous integration servers’’’. It is going to build all the packages that are defined within Rock, which is probably not what you want. You probably want to install base system and then cherry-pick the packages you want. Have a look in the package directory, and add the package names to the layout section in autoproj/manifest. For instance, if you want to get the Xsens IMU component, the layout section should look like:

  layout:
     - rock.base
     - rock.toolchain
     - drivers/orogen/xsens_imu
  

Maintaining a Rock installation

Once Rock is installed, you can update your installation by going into the root of the installation folder and do

autoproj update
autoproj build

You might have to reload the env.sh script after that as well, to export updated environment variables into your current shell. Simply opening a new console will do the trick (given you have added sourcing env.sh to your .bashrc).