Robotics Systems Commons

h1. Dependencies

* Boost >= 1.38 (for hardy available in the gar-installer, 1.34.1 untested)

* CMake (tested with 2.8)

* optional

** Doxygen for API generation

** Lcov for code coverage analysis

h1. Contents

h2. Logging Adapter

Several different logging systems exist with different advantages and dependencies. E.g. log4cxx heavily relies on APR which is a huge dependency to built i.e. for embedded systems like Nao. To decouple libraries from concrete logging implementations and their dependencies, RSC contains a flexible adaption layer that can utilize different logging mechanisms through one interface. If e.g. log4cxx is available, a client using the RSC logging system can use log4cxx through the provided interfaces. If no versatile logging system is available, RSC falls back on a simple console logging mechanism without any dependencies. Hence, client code does not need to be recompiled for changing the logging system.

Currently the linker call decides which logging mechanisms are available by linking their adapter shared libraries to the client. A plugin system is planned to remove the necessity of calling the linker.

h2. CMake Support Library

RSC contains different CMake scripts and macros which are generally useful. These include:

* Find macros for various software packages

* *EnableConverageReport*: Support for html code coverage reports on GCC using gcov and lcov.

* *CheckInitMethod*: Checks which compiler-specific method can be used to execute before the main method begins. This is e.g. useful to install extensions

* *InstallFilesRecursive*: A macro to install files while preserving their folder structure. The normal install macro of CMake copies all given files into a flat list at the target location.

* *ParseArguments*: Helper to parse arguments to CMake macros and functions with UPPERCASE keywords to separate lists.

All CMake files are installed to @$prefix/share/cmake/Modules@ and available in the repository at source:/trunk/rsc/cmake.

h2. To be continued