Skip to content

ipa320/build_state_logger

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

build_state_logger

Ever wondered in which state your workspace was, when you called catkin_make install? This package will help you with this.

It creates a build_state.log file showing you detailed information about your workspace. Which repository was in which state? Have any files been changed?

Installation

This tool depends on the gitpython module. To install gitpython, simply run pip install gitpython.

Usage

There are several ways to use this tool.

  1. Via CMake during the build and install step of catkin_make by cloning the repository.
  2. By manually calling the tool via rosrun.

Via CMake

Simply clone this repository into your catkin workspace. When compiling your workspace, it automatically creates the build_state.log within the build_state_logger directory. When you then install your workspace, the build_state.log file will be installed in install/share/build_state_logger.

The tool searches all repositories in <YOUR_WORKSPACE>/src directory.

Note that in the current state, the log file will be generated on each run of CMake, i.e. at each call to catkin_make and catkin_make install

Via rosrun

As this is a regular ROS package this tool can also be used as any other python node. Just make sure it is on your ROS_PACKAGE_PATH and call

rosrun build_state_logger build_state

The build_state.log will be put into the current working directory. Optionally, you can specify the output path on the command line:

rosrun build_state_logger build_state <OUTPUTPATH>

Licensing

This package is licensed under LGPL. gitpyhon is licensed under the new BSD license.