RT-SLAM is currently provided as-is and is not standalone, and is not advised to people who don't feel very comfortable with manual installation from source. Installation will be more simple when the first release will be made. Currently you need to install our modular development environment Jafar, and the required dependencies.
Installation is possible with all Linux flavors and MacOS X.
Standard development tools
When you install these libraries with your system package manager, you have to also install the development packages (in general named package-devel or package-dev).
boost >= 1.40
svn co http://svn.boost.org/svn/boost/sandbox/numeric_bindings boost-sandbox/
qt4 (optional, for 2D display)
gdhe (optional, for 3D display)
viam (optional, for live use of firewire cameras)
MTI driver (optional, for live use of XSens MTi IMU)
git clone git://trac.laas.fr/git/robots/jafar/jafar.git
We will later refer to the directory where you cloned jafar as $JAFAR_DIR.
Configure the build system
Jafar uses cmake.
If you need to modify RT-SLAM, you may want to create two directories build_debug and build_release and run cmake in each of them with the appropriate -DCMAKE_BUILD_TYPE option.
The additional common options you may want to pass to cmake are:
-DPATH_TO_BOOST_SANDBOX=/path/to/boost-sandbox to tell cmake where to find boost-sandbox (such that $PATH_TO_BOOST_SANDBOX/boost/numeric/bindings exists and is an absolute path)
-DBOOST_ROOT=/path/to/boost to tell cmake which boost installation to use, if there are several of them or if it is in a non-standard path (such that $BOOST_ROOT/include/boost exists and is an absolute path)
-DOpenCV_ROOT_DIR=/path/to/opencv to tell cmake where to find opencv (such that $OpenCV_ROOT_DIR/include/opencv exists and is an absolute path)
-DCMAKE_BUILD_TYPE=debug or -DCMAKE_BUILD_TYPE=release to choose a compilation profile, you can have both in two different build dirs at the same time, to easily switch between them
You may want to save the cmake command with its arguments in some file $JAFAR_DIR/cmake-command.txt in case you have to do it again from the beginning.
If you have some trouble making it find the right dependencies, sometimes it is useful to remove the CMakeCache.txt file in the build directory before running the cmake command again.
don't fetch the jafar module gdhe for 3D display with bin/jafar_checkout gdhe if you didn't install the gdhe library or are not willing to, as the project won't compile. If you fetched it by mistake, you can remove it by simply deleting the $JAFAR_DIR/modules/gdhe folder.
If you want to compile faster, you can do make -jn instead of make with n the number of real CPU cores on your system plus one (-j3 for dualcore, -j5 for quadcore).
bin/jafar_update stash cd build make rebuild_cache make
If you made some modifications, you may want to get an overview of them with bin/jafar_status.