sysutils/console-bridge

Logging for ROS-independent applications
Directory:
sysutils/console-bridge (package's history)
Package version:
console-bridge-0.2.7
Home page:
http://wiki.ros.org/console_bridge
License:
modified-bsd
Source archive:
https://github.com/ros/console_bridge/archive/0.2.7.tar.gz
Description:
console_bridge is a ROS-independent package that provides logging calls that mirror those found in rosconsole, but for applications that are not necessarily using ROS. Normally in ROS C++ code, developers can log data via rosconsole using the macros ROS_DEBUG, ROS_INFO, ROS_WARN, and ROS_ERROR. These logging messages are not only outputted to the screen (depending on log level of course), but are also published to /rosout so that other ROS nodes can subscribe to them. Applications like rqt and its predecessor rxconsole provide graphical interfaces for seeing logs during application runtime. The problem with this approach is that libraries that are meant to run without ROS infrastructure and/or may not want or need the log publishing cannot use the traditional rosconsole. This is where console_bridge comes in.
Run dependencies:
boost-libs>=1.34.1, boost-libs>=1.34.1, libstdc++
Build dependencies:
boost-headers>=1.34.1, cmake>=2.6, digest>=20080510, g++>=3, gcc>=3, pax, pkg_install>=20110805.7, tnftp>=20130505~ssl
General options:
debug
Produce debugging information for binary programs
c++-compiler alternatives:
g++
Use the GNU C++ compiler
clang++
Use the LLVM C++ compiler
ccache-g++
Use ccache and the GNU C++ compiler
ccache-clang++
Use ccache and the LLVM C++ compiler
c-compiler alternatives:
gcc
Use the GNU C compiler
clang
Use the LLVM C compiler
ccache-gcc
Use ccache and the GNU C compiler
ccache-clang
Use ccache and the LLVM C compiler