Crates.io | catkin-bloom |
lib.rs | catkin-bloom |
version | 0.0.2 |
source | src |
created_at | 2022-06-21 10:19:34.207761 |
updated_at | 2022-06-21 10:20:40.988316 |
description | build entire catkin workspace using bloom |
homepage | |
repository | https://github.com/tavo-robotas/catkin-bloom |
max_upload_size | |
id | 610136 |
size | 35,626 |
catkin-bloom is an utility program meant to help building ROS packages locally, without resorting to deploying the complicated ROS build farm.
catkin-bloom primarily aims to support running under ROS docker images, thus debian packaging is currently supported. In addition, this is a very early version that only supports ROS melodic on Ubuntu bionic. More flexibility is under way.
You can build the docker image using:
docker build -t catkin-bloom .
Then, run the image with appropriate mounts:
docker run -v "${PWD}/src":/workspace -v "${PWD}/repo":/repo -it --rm catkin-bloom --repo-path /repo -j8 /workspace
os-name
, os-version
and ros-distro
arguments are automatically set based on the docker image environment.
If no arguments are supplied, repo-path
defaults to /repo
, jobs
defaults to 8, and the workspace path defaults to /workspace
.
First, install rust toolchain, and install catkin-bloom through it:
cargo install --path .
Or, when this package is on crates.io:
cargo install catkin-bloom
Then, install required dependencies:
apt install dh-make python-bloom fakeroot
Then, run the program on the workspace source:
catkin-bloom -r /tmp/bloom src
The resulting debs will be found under /tmp/bloom directory. Repository will be automatically added to /etc/apt/sources.list.d
, and /etc/ros/rosdep/sources.list.d
.
In addition, this program will install all of those packages, to cleanup, run the following:
apt remove $(cd /tmp/bloom; for p in *.deb; do echo $p | cut -f1 -d"_"; done)
The way catkin-bloom works is by walking the entire workspace, parsing dependencies, and sorting packages in a way that all dependencies are built before the dependents. Cycles are assumed to not exist (since they are illegal anyways). The packages are then ordered in tiers, where all packages in a single tier are completely independent (and may only depend on the lower tiers). See below figure:
T 1 | T 2 | T 3 | T 4
-----------+-----------+-----------+-----------
+---+ +---+ +---+
| A |------>| D |---------------+-->| H |
+---+ +---+ | +---+
| |
+-----+-----------------------+
| |
+---+ | +---+ +---+ |
| B |---+-->| E |------>| F | |
+---+ +---+ +---+ |
| | |
+-----------+-----+ |
| |
+---+ | +---+ |
| C |---------------+-->| G |---+
+---+ +---+
Packages A, B, C can be built concurrently, speeding up the process. Same with D, E, and F, G respectively.