colcon-cargo-ros2

Build Rust ROS 2 packages with automatic message binding generation.

colcon-cargo-ros2 is a colcon extension that enables seamless integration of Rust packages in ROS 2 workspaces. It automatically generates Rust bindings for ROS message types, manages dependencies, and installs packages in ament-compatible layout.

Features

Automatic Binding Generation: Generates Rust bindings for messages, services, and actions on-demand
Smart Caching: SHA256-based checksums for fast incremental builds
Workspace-Level Bindings: Bindings generated once and shared across all packages
Zero Configuration: Just add dependencies to Cargo.toml - bindings are handled automatically
Ament Compatible: Installs to standard ament locations for seamless ROS 2 integration

Installation

From PyPI (Recommended)

pip install --user colcon-cargo-ros2

From Source

git clone https://github.com/jerry73204/colcon-cargo-ros2.git
cd colcon-cargo-ros2
pip install --user packages/colcon-cargo-ros2/

If you install into a virtualenv

Create it with --system-site-packages:

python3 -m venv --system-site-packages ~/.venvs/ros
~/.venvs/ros/bin/pip install colcon-cargo-ros2

An isolated virtualenv breaks the other packages in your workspace, not this one. ROS's Python toolchain comes from apt — python3-empy, python3-lark, python3-catkin-pkg and the rest, in /usr/lib/python3/dist-packages — and it expects to find exactly those. CMake runs whichever python3 is first on PATH, so a package built with rosidl_generate_interfaces invokes ROS's own generators under an interpreter that cannot see them:

ModuleNotFoundError: No module named 'lark'
AttributeError: module 'em' has no attribute 'BUFFERED_OPT'

The second is empy specifically. rosidl_adapter is written against the 3.3.4 that python3-empy ships; PyPI's 4.x is not a drop-in, and colcon-core declares empy with no upper bound, so a virtualenv with nothing visible resolves 4.x. --system-site-packages puts the apt packages back on the path, and pip then treats the requirement as already satisfied.

pip install --user has the same effect for the same reason — dist-packages stays visible, so nothing gets replaced.

Neither error mentions Rust or this extension, which is why they are worth naming here.

Quick Start

1. Create a ROS 2 Workspace

mkdir -p ~/ros2_ws/src
cd ~/ros2_ws

2. Create a Rust ROS 2 Package

cd src
cargo new --bin my_robot_node
cd my_robot_node

3. Add ROS Dependencies

Cargo.toml:

[package]
name = "my_robot_node"
version = "0.1.0"
edition = "2021"

[dependencies]
rclrs = "0.7"
std_msgs = "*"
geometry_msgs = "*"

package.xml:

<?xml version="1.0"?>
<?xml-model href="http://download.ros.org/schema/package_format3.xsd" schematypens="http://www.w3.org/2001/XMLSchema"?>
<package format="3">
  <name>my_robot_node</name>
  <version>0.1.0</version>
  <description>Example Rust ROS 2 node</description>
  <maintainer email="you@example.com">Your Name</maintainer>
  <license>Apache-2.0</license>

  <buildtool_depend>ament_cargo</buildtool_depend>

  <depend>std_msgs</depend>
  <depend>geometry_msgs</depend>

  <export>
    <build_type>ament_cargo</build_type>
  </export>
</package>

src/main.rs:

use rclrs::CreateBasicExecutor;

fn main() -> Result<(), Box<dyn std::error::Error>> {
    // Initialize ROS context from environment
    let context = rclrs::Context::default_from_env()?;

    // Create executor (manages event loop)
    let executor = context.create_basic_executor();

    // Create node through executor
    let node = executor.create_node("minimal_publisher")?;

    // Create publisher for std_msgs/String on the "chatter" topic
    let publisher = node.create_publisher::<std_msgs::msg::String>("chatter")?;

    // Publish a few messages
    for i in 0..5 {
        let mut msg = std_msgs::msg::String::default();
        msg.data = format!("Hello from Rust! Message #{}", i);

        println!("Publishing: '{}'", msg.data);
        publisher.publish(msg)?;

        std::thread::sleep(std::time::Duration::from_millis(500));
    }

    println!("✓ Published 5 messages successfully!");
    Ok(())
}

4. Build with colcon

cd ~/ros2_ws
source /opt/ros/jazzy/setup.bash  # Or your ROS 2 distro
colcon build --symlink-install

The extension will:

Discover ROS interface dependencies from package.xml <depend> tags
Generate Rust bindings for std_msgs and geometry_msgs
Write .cargo/config.toml with patches and linker flags
Build your Rust package with cargo
Install binaries to install/my_robot_node/lib/my_robot_node/

5. Run Your Program

source install/setup.bash
ros2 run my_robot_node my_robot_node

Expected output:

Publishing: 'Hello from Rust! Message #0'
Publishing: 'Hello from Rust! Message #1'
Publishing: 'Hello from Rust! Message #2'
Publishing: 'Hello from Rust! Message #3'
Publishing: 'Hello from Rust! Message #4'
✓ Published 5 messages successfully!

Package Structure

For colcon-cargo-ros2 to recognize your package:

Both files required: package.xml AND Cargo.toml in the package root
Build type: package.xml must specify <build_type>ament_cargo</build_type> in the <export> section
Dependencies: List ROS dependencies in both Cargo.toml and package.xml

Verify packages are detected:

$ colcon list
my_robot_node   src/my_robot_node   (ros.ament_cargo)

Building

Basic Commands

# Build all packages
colcon build

# Build specific package
colcon build --packages-select my_robot_node

# Build with release optimizations
colcon build --cargo-args --release

# Verbose output
colcon build --event-handlers console_direct+

Using Custom Interfaces

Custom interface packages follow the standard ROS 2 procedure (CMake-based with rosidl_generate_interfaces). Add them as dependencies in both files:

package.xml (required for binding generation):

<depend>my_custom_interfaces</depend>

Cargo.toml:

[dependencies]
my_custom_interfaces = "*"

Bindings will be generated automatically during the build.

How It Works

Workspace-Level Binding Generation

When building a colcon workspace, colcon-cargo-ros2:

Discovers Packages: Finds all ROS dependencies via ament index
Generates Bindings: Creates Rust bindings in build/<pkg>/rosidl_cargo/ for each interface package
Creates Config: Generates .cargo/config.toml in each Cargo workspace/crate with [patch.crates-io] entries, [build] rustflags and target-dir, and [env] for build scripts
Builds: Runs cargo build from workspace root (config is picked up automatically from .cargo/config.toml)
Installs: Copies binaries and creates ament markers

Workspace Structure:

ros2_ws/
├── build/
│   ├── std_msgs/
│   │   └── rosidl_cargo/       # Rust bindings for std_msgs
│   │       └── std_msgs/
│   ├── geometry_msgs/
│   │   └── rosidl_cargo/       # Rust bindings for geometry_msgs
│   │       └── geometry_msgs/
│   └── my_interfaces/
│       └── rosidl_cargo/       # Rust bindings for custom interfaces
│           └── my_interfaces/
├── build/.cargo_target/        # Cargo build artifacts (shared, out of src/)
├── install/
│   ├── my_robot_node/
│   │   ├── lib/my_robot_node/  # Binaries
│   │   └── share/              # Metadata
│   └── my_interfaces/
└── src/
    ├── my_robot_node/
    │   ├── Cargo.toml
    │   ├── package.xml
    │   ├── .gitignore          # Auto-generated (ignores .cargo/config.toml)
    │   └── .cargo/
    │       └── config.toml     # Auto-generated (patches, flags, env, target-dir)
    └── my_interfaces/

Working with `cargo` Directly

After one colcon build, plain cargo commands work from any package directory with no flags and no sourced environment:

cd src/my_robot_node
cargo build
cargo run
cargo test
cargo clippy

The generated .cargo/config.toml is what makes this work. It sits at the Cargo workspace root (or the crate root for standalone crates) and carries four things:

Section	Purpose
`[patch.crates-io]`	Resolves `std_msgs = "*"` to the generated crate under `build/`
`[build] rustflags`	`-L` linker search paths, plus rpath entries so built binaries find ROS libraries at run time. Workspace-internal libraries get `$ORIGIN`-relative entries too, so a workspace that is moved, renamed, or whose `install/` tree is copied elsewhere keeps working
`[build] target-dir`	Puts cargo artifacts under `build/.cargo_target/`, keeping `src/` clean while colcon and manual cargo share one cache
`[env]`	`AMENT_PREFIX_PATH` for generated build scripts, with `force = false` so a sourced environment still wins

Key details:

Adding a message dependency means editing both package.xml (<depend>) and Cargo.toml, then re-running colcon build — cargo alone cannot generate bindings
The rosidl_runtime_rs version generated crates depend on is derived from your packages: whatever they declare, or the version implied by their rclrs (0.6 → 0.5, 0.7 → 0.6). It has to match, or cargo ends up with two incompatible copies. --rosidl-runtime-rs-version overrides it
A Cargo workspace resolves as a unit, so one member's unresolvable dependency fails its siblings
User entries in an existing .cargo/config.toml are preserved via comment-based markers
The config is added to .gitignore automatically (its paths are machine-specific); opt out with --no-gitignore
rpath baking can be disabled with --no-rpath, after which binaries need a sourced ROS environment to run
A target-dir you set yourself is left alone

When cargo reports something that does not match the above, run:

colcon-cargo-ros2-doctor

It checks the ROS environment, the generated config, every patched crate directory, binding freshness, and package.xml declarations, then prints the fix for the first thing that is wrong.

The same command installs a small CLI for the operations colcon build performs, should you need one of them on its own:

colcon-cargo-ros2 bindgen --package std_msgs --output build/bindings
colcon-cargo-ros2 install --install-base install/my_node
colcon-cargo-ros2 clean
colcon-cargo-ros2 doctor
``` See [docs/troubleshooting.md](docs/troubleshooting.md) for the individual error messages.

### IDE Support

The same `.cargo/config.toml` makes IDEs (RustRover, rust-analyzer, VS Code) resolve all ROS message dependencies automatically — `cargo metadata` succeeds, so autocomplete, go-to-definition and type checking work without extra configuration.

### Benefits

- **IDE Integration**: Full autocomplete and type checking for ROS message types
- **Per-Package Organization**: Bindings follow ROS conventions (like `rosidl_cmake/`)
- **Fast Builds**: Intelligent caching skips regeneration when possible
- **Clean Workspace**: `colcon clean` removes all generated code; cargo artifacts never land in `src/`
- **Portable**: Patch paths are relative, and the generated config is git-ignored for you (rustflags contain absolute paths)

## Advanced Features

### Installing Additional Files with `[package.metadata.ros]`

ROS 2 packages often need to install additional files beyond binaries (launch files, config files, URDF models, RViz configs, meshes, etc.). Use the `[package.metadata.ros]` section in `Cargo.toml` to specify these files:

```toml
[package]
name = "my_robot"
version = "0.1.0"

[dependencies]
rclrs = "0.7"
std_msgs = "*"

[package.metadata.ros]
install_to_share = ["launch", "config", "urdf", "README.md"]
install_to_include = ["include"]
install_to_lib = ["scripts"]

Supported Keys

install_to_share: Files/directories installed to install/<pkg>/share/<pkg>/
- Launch files, config files, URDF models, RViz configs, meshes, documentation
install_to_include: Headers installed to install/<pkg>/include/<pkg>/
- C/C++ headers for FFI libraries
install_to_lib: Scripts/utilities installed to install/<pkg>/lib/<pkg>/
- Helper scripts and executables

Example: Robot Description Package

[package]
name = "my_robot_description"
version = "0.1.0"

[lib]
# Library-only package (no binaries)

[package.metadata.ros]
install_to_share = ["urdf", "meshes", "launch", "rviz"]

Project structure:

my_robot_description/
├── Cargo.toml
├── package.xml
├── src/lib.rs
├── urdf/
│   ├── robot.urdf.xacro
│   └── robot.urdf
├── meshes/
│   ├── base.stl
│   └── arm.dae
├── launch/
│   └── display.launch.xml
└── rviz/
    └── default.rviz

After colcon build:

install/my_robot_description/
└── share/my_robot_description/
    ├── urdf/              # Directory with all URDF files
    ├── meshes/            # Directory with all mesh files
    ├── launch/            # Directory with launch files
    ├── rviz/              # Directory with RViz configs
    ├── rust/              # Source code (automatic)
    └── package.xml        # Metadata (automatic)

Troubleshooting

"Package not found in ament index"

Make sure the ROS 2 environment is sourced:

source /opt/ros/jazzy/setup.bash

"error: failed to select a version"

This usually means bindings weren't generated. Try:

# Clean and rebuild
rm -rf build install
colcon build

Build fails with linking errors

Ensure all dependencies are listed in both Cargo.toml and package.xml:

<depend>std_msgs</depend>
<depend>geometry_msgs</depend>

Requirements

Python: 3.8 or later
ROS 2: Humble, Iron, or Jazzy
Rust: 1.70 or later (stable toolchain)
colcon: Latest version

License

Apache-2.0 (compatible with ROS 2 ecosystem)

Contributing

See CONTRIBUTING.md for development setup, architecture details, and guidelines.

Related Projects

ros2_rust - Official Rust bindings for ROS 2
r2r - Alternative Rust bindings
colcon - Build tool for ROS 2

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

colcon_cargo_ros2-0.5.2.tar.gz (202.2 kB view details)

Uploaded Aug 27, 2026 Source

Built Distributions

If you're not sure about the file name format, learn more about wheel file names.

The dropdown lists show the available interpreters, ABIs, and platforms. Enable javascript to be able to filter the list of wheel files.

colcon_cargo_ros2-0.5.2-cp313-cp313-win_amd64.whl (740.6 kB view details)

Uploaded Aug 27, 2026 CPython 3.13Windows x86-64

colcon_cargo_ros2-0.5.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (831.6 kB view details)

Uploaded Aug 27, 2026 CPython 3.13manylinux: glibc 2.17+ x86-64

colcon_cargo_ros2-0.5.2-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (769.4 kB view details)

Uploaded Aug 27, 2026 CPython 3.13manylinux: glibc 2.17+ ARM64

colcon_cargo_ros2-0.5.2-cp313-cp313-macosx_11_0_arm64.whl (735.7 kB view details)

Uploaded Aug 27, 2026 CPython 3.13macOS 11.0+ ARM64

colcon_cargo_ros2-0.5.2-cp313-cp313-macosx_10_12_x86_64.whl (765.1 kB view details)

Uploaded Aug 27, 2026 CPython 3.13macOS 10.12+ x86-64

colcon_cargo_ros2-0.5.2-cp312-cp312-win_amd64.whl (742.2 kB view details)

Uploaded Aug 27, 2026 CPython 3.12Windows x86-64

colcon_cargo_ros2-0.5.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (832.1 kB view details)

Uploaded Aug 27, 2026 CPython 3.12manylinux: glibc 2.17+ x86-64

colcon_cargo_ros2-0.5.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (769.7 kB view details)

Uploaded Aug 27, 2026 CPython 3.12manylinux: glibc 2.17+ ARM64

colcon_cargo_ros2-0.5.2-cp312-cp312-macosx_11_0_arm64.whl (736.6 kB view details)

Uploaded Aug 27, 2026 CPython 3.12macOS 11.0+ ARM64

colcon_cargo_ros2-0.5.2-cp312-cp312-macosx_10_12_x86_64.whl (766.2 kB view details)

Uploaded Aug 27, 2026 CPython 3.12macOS 10.12+ x86-64

colcon_cargo_ros2-0.5.2-cp311-cp311-win_amd64.whl (744.8 kB view details)

Uploaded Aug 27, 2026 CPython 3.11Windows x86-64

colcon_cargo_ros2-0.5.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (835.3 kB view details)

Uploaded Aug 27, 2026 CPython 3.11manylinux: glibc 2.17+ x86-64

colcon_cargo_ros2-0.5.2-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (772.4 kB view details)

Uploaded Aug 27, 2026 CPython 3.11manylinux: glibc 2.17+ ARM64

colcon_cargo_ros2-0.5.2-cp311-cp311-macosx_11_0_arm64.whl (740.7 kB view details)

Uploaded Aug 27, 2026 CPython 3.11macOS 11.0+ ARM64

colcon_cargo_ros2-0.5.2-cp311-cp311-macosx_10_12_x86_64.whl (766.1 kB view details)

Uploaded Aug 27, 2026 CPython 3.11macOS 10.12+ x86-64

colcon_cargo_ros2-0.5.2-cp310-cp310-win_amd64.whl (743.1 kB view details)

Uploaded Aug 27, 2026 CPython 3.10Windows x86-64

colcon_cargo_ros2-0.5.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (835.0 kB view details)

Uploaded Aug 27, 2026 CPython 3.10manylinux: glibc 2.17+ x86-64

colcon_cargo_ros2-0.5.2-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (772.1 kB view details)

Uploaded Aug 27, 2026 CPython 3.10manylinux: glibc 2.17+ ARM64

colcon_cargo_ros2-0.5.2-cp310-cp310-macosx_11_0_arm64.whl (739.7 kB view details)

Uploaded Aug 27, 2026 CPython 3.10macOS 11.0+ ARM64

colcon_cargo_ros2-0.5.2-cp310-cp310-macosx_10_12_x86_64.whl (765.5 kB view details)

Uploaded Aug 27, 2026 CPython 3.10macOS 10.12+ x86-64

colcon_cargo_ros2-0.5.2-cp39-cp39-win_amd64.whl (744.8 kB view details)

Uploaded Aug 27, 2026 CPython 3.9Windows x86-64

colcon_cargo_ros2-0.5.2-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (837.0 kB view details)

Uploaded Aug 27, 2026 CPython 3.9manylinux: glibc 2.17+ x86-64

colcon_cargo_ros2-0.5.2-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (773.7 kB view details)

Uploaded Aug 27, 2026 CPython 3.9manylinux: glibc 2.17+ ARM64

colcon_cargo_ros2-0.5.2-cp39-cp39-macosx_11_0_arm64.whl (742.0 kB view details)

Uploaded Aug 27, 2026 CPython 3.9macOS 11.0+ ARM64

colcon_cargo_ros2-0.5.2-cp39-cp39-macosx_10_12_x86_64.whl (767.4 kB view details)

Uploaded Aug 27, 2026 CPython 3.9macOS 10.12+ x86-64

colcon_cargo_ros2-0.5.2-cp38-cp38-win_amd64.whl (744.9 kB view details)

Uploaded Aug 27, 2026 CPython 3.8Windows x86-64

colcon_cargo_ros2-0.5.2-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (837.4 kB view details)

Uploaded Aug 27, 2026 CPython 3.8manylinux: glibc 2.17+ x86-64

colcon_cargo_ros2-0.5.2-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (773.8 kB view details)

Uploaded Aug 27, 2026 CPython 3.8manylinux: glibc 2.17+ ARM64

colcon_cargo_ros2-0.5.2-cp38-cp38-macosx_11_0_arm64.whl (742.0 kB view details)

Uploaded Aug 27, 2026 CPython 3.8macOS 11.0+ ARM64

colcon_cargo_ros2-0.5.2-cp38-cp38-macosx_10_12_x86_64.whl (767.5 kB view details)

Uploaded Aug 27, 2026 CPython 3.8macOS 10.12+ x86-64

File details

Details for the file colcon_cargo_ros2-0.5.2.tar.gz.

File metadata

Download URL: colcon_cargo_ros2-0.5.2.tar.gz
Upload date: Aug 27, 2026
Size: 202.2 kB
Tags: Source
Uploaded using Trusted Publishing? Yes
Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for colcon_cargo_ros2-0.5.2.tar.gz
Algorithm	Hash digest
SHA256	`f7149144e50fd9bd77e9482963d57614a197f432a2a6f5b4720642b91dec6c40`
MD5	`26d527c09fd4b4d1f18df4f12f2f6d8a`
BLAKE2b-256	`7638aadc284cf33ad0a23cefabe815dba8717163c06cd21ff0dfc33623b067f5`

Algorithm	Hash digest
SHA256	`89dae09fdad406f8753683f0c4b593e90da7e348548a4887c83dde5f5b35df72`
MD5	`47211a66572f5a528da450c35dc47d26`
BLAKE2b-256	`ccd49a28edc171231a89a19fafe3886f65f6d8a7b528eb1af06dc2b0d0382a92`

Algorithm	Hash digest
SHA256	`add79f16abcf9d53fe2838aedee11c5ebf5f434fec794c4f8dd73a76a15b56bc`
MD5	`72c557ea9d2f10f384876bb25e0cbedf`
BLAKE2b-256	`62dfab6ccf9794f03a0a35b5868d45c120edf576c8e0a3b3fda5242c621f91bf`

Algorithm	Hash digest
SHA256	`62d4891ff8de170990aa3e4d2c6ff24f6e9a600b04d9f70fc1f72bf5cb766393`
MD5	`b214148ac4f1fd02baae73c20f21b9ff`
BLAKE2b-256	`fd024984fa0b2d4a3c33dfa3e2a1656e91b66d26cb03e2c74cb6e75b7d7a8758`

Algorithm	Hash digest
SHA256	`4216e7a4e81f2936fd0df197a692850f21478a68af29808d0d755bca5ab33af6`
MD5	`f46bde79efb760e79e5f0a19afe16920`
BLAKE2b-256	`92162dfa67afdf140724dc0e010ef2d6b2449093812186ab89fd3f54e0139d6a`

Algorithm	Hash digest
SHA256	`a673a3441a74d9dd791f138221ea93eb630a28833cb14c9a075acbd09c5fb6e4`
MD5	`0983260f76542068cbdca1b8a88117cf`
BLAKE2b-256	`96f15873759fa0412388cae8e2eefc83de181182a0b0e7ed768d0ab4a8536bcf`

Algorithm	Hash digest
SHA256	`14b41dfedc58fa344178eebf173836103bc966415c8ac20e37086d028337b084`
MD5	`a5b96e90eb376d1661d64cdd2374c318`
BLAKE2b-256	`d86d4748b826c8081d39de2ae353ee61395d10509d81ed4c38a6904498147d98`

Algorithm	Hash digest
SHA256	`414ceee27f10bfa972b78aa0e0886b2ce2429d8ff652934f5993192997130a41`
MD5	`f8dbfe5f770daf479d2ac86377dd39d9`
BLAKE2b-256	`df510e0c51a9bf4d08f44d514a2c4f0ba6ed729901f433412adad57b91b47b29`

Algorithm	Hash digest
SHA256	`84ff81b2379c39a9b238dd64288e03b9033c64625fc70fc94ada71cc507c6dce`
MD5	`2f27470eeaff642ada9560714442a8f7`
BLAKE2b-256	`8017e5d5c4ddb289b42872dca67560112fb30be5e75cc24c9d1b9c2163ec27d1`

Algorithm	Hash digest
SHA256	`244f82f2a9a44894a3cf80448e0c1be5187bd74b304b0e83f0706f4567870f94`
MD5	`7ebe336a91be8f927cfabdb73569f4ea`
BLAKE2b-256	`7011c0b6ba35a39818e9b4d9feea87a0d59af9c2815cd109a3cd3e9e5367c79a`

Algorithm	Hash digest
SHA256	`93aa4c84a79d33b43be9354ad465922d328464963c8498f6262179d8f879a7fb`
MD5	`a7f02689d1210546e6e685d861088a7e`
BLAKE2b-256	`4b303d4216a51ed2af2c7b0fd5b08155ecaff1af3a8bb2607128e86b30a3b33f`

Algorithm	Hash digest
SHA256	`98b61da8d3219b810093c013227adf9376624766657e8209caf19a5d68241bf2`
MD5	`e2c9fba591f943d80412f7aea6ee147b`
BLAKE2b-256	`a5f8b52376045e4f40cf07e577abfdebb1d830b37688fe03141d6b8409a440ea`

Algorithm	Hash digest
SHA256	`1296c96f528d2562721b8eec20ff69d344804b8e9ba319d0c36ffcfa5287806d`
MD5	`dbffb395851dafd2a9a298b7b8734f69`
BLAKE2b-256	`76d4beee3487783b0a63462ea01be6b86f83a8eb1f85043c1969c2b5052a6215`

Algorithm	Hash digest
SHA256	`a02fcbf033ee407dc75e770b4b5d20b2ad5542dbbb26e7d1358dcc936d95c0d8`
MD5	`a098b479e691a779109817707618ca5d`
BLAKE2b-256	`2441a31d882551d30fe2fe40ddf8597fa889593c50ccd8e7f3386274710afb42`

Algorithm	Hash digest
SHA256	`1ebca8b679b84d2c0bf2fd1a405ad03413157bd7a4961e5b177eddd2c3c821bd`
MD5	`87b066b4a568216946f70bda1d30088e`
BLAKE2b-256	`cc40da347d2a2e11722a95d6dba4a5aa6ade339b437aff27b94e2482fa29c290`

Algorithm	Hash digest
SHA256	`634db444349f8a9c96d57fb82a0dcb25586948290008ec794c64ee6d6b4c4476`
MD5	`c43f8f0311e11e8c4414c9bdd0fe96b9`
BLAKE2b-256	`ba72ecc90b9155fc976e19a6f0c8ed1dba1308c0314ae726da5e3bc83e13e8d8`

Algorithm	Hash digest
SHA256	`2a3b8f287aa206f4d3afed7eef21a13fcfb2fe38ac967bb79080aac96a38c8b5`
MD5	`88bea9adcda5fdddf7fbe8c0cf582b9c`
BLAKE2b-256	`96c1a725b74347f5f9a5c994c21ff674925e639ef6524ae663440a731847935d`

Algorithm	Hash digest
SHA256	`8d72c6c3dc5a9c175564f7ad76d230261ff158e5e1381cc6a919ca0f2214c9c1`
MD5	`a14febe63a9596c25369451098975c9e`
BLAKE2b-256	`e05261edfcca636a0f875dc7b2a1af0207e167bd1462854f1424596a2f60a9f0`

Algorithm	Hash digest
SHA256	`01310fc5ae6cb870ef401b1961ec03a84afeb2234c3e8fa3ae66720ca3672877`
MD5	`07fb50c47ca4ae0eb76f393fdb366e77`
BLAKE2b-256	`3f414e1cde9024eceed5e48f9806b2e5b7a8fcc4b636070b9d5758cbb6c0eeec`

Algorithm	Hash digest
SHA256	`d0cdc52f84231baeabc0ab61531d95c6de6563d3b54e613e81530854bf7cbbce`
MD5	`2f46f36fe41e564b2ceef94474bb137d`
BLAKE2b-256	`5b158ea3bf1b261baf294efeed21dbc612736e78c75446abbc6da30122aa7ef4`

Algorithm	Hash digest
SHA256	`824550f550c3c1beb8bf4f8c337ca5b600e1d66f7bae5069610517cc99173c94`
MD5	`41428faa31b80534df1624812cf20c8c`
BLAKE2b-256	`bada2926a2cf8e9aee8e8092e7a42727cf6af02dfd859fd470aa7a363f977777`

colcon-cargo-ros2 0.5.2

colcon-cargo-ros2

Features

Installation

From PyPI (Recommended)

From Source

If you install into a virtualenv

Quick Start

1. Create a ROS 2 Workspace

2. Create a Rust ROS 2 Package

3. Add ROS Dependencies

4. Build with colcon

5. Run Your Program

Package Structure

Building

Basic Commands

Using Custom Interfaces

How It Works

Workspace-Level Binding Generation

Working with cargo Directly

Supported Keys

Example: Robot Description Package

Troubleshooting

"Package not found in ament index"

"error: failed to select a version"

Build fails with linking errors

Requirements

License

Contributing

Related Projects

Project links

Key dates

1 maintainer

Credits

GitHub Statistics

License

Requires

Tags

Classifiers

Download files

Source Distribution

Built Distributions

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

File hashes

Provenance

File details

File metadata

Working with `cargo` Directly

Algorithm	Hash digest
SHA256	`d47e32f5f0a936af16586339ef2176606d2ba74f9dbbcc76ad6cbf6a1c228607`
MD5	`4721f434430fc9d9e0be26914a620481`
BLAKE2b-256	`5da2a8f2a38b41bc246dc02bb45fe3bd80e562b83c0f714d9fe7df03028e43e2`

Algorithm	Hash digest
SHA256	`8ade0dc1efa3edb1f730c16bc98feb153d4fcd881ba307dc54885f14fce9508c`
MD5	`8e4ed336bcceeaac7f75ad3fe2279118`
BLAKE2b-256	`90401ede7d7041b1dfb7dcb6adfd1a715f22bec5a9ae732cc32cf9c694dd8360`

Algorithm	Hash digest
SHA256	`7a2f5fb787c45e72cc18b8b7d84a226bf736293e1116d3a10a08605f0f93f28e`
MD5	`88afa60298de455ec98fb1001884ca88`
BLAKE2b-256	`77f7e11814b1b88f93e961b841c5bd0ebf0af810579ae0e7f346033f045374d4`

Algorithm	Hash digest
SHA256	`82b16fb3c666634fd1bb0d22fd64162a6988ba291f35b137ea561dead5e6bfd4`
MD5	`c76c2e3f59f298899fe0ebd779df06ca`
BLAKE2b-256	`b60209cf9d30565afb94432e6851308df9838bc8c3c4f165b9b419e1ad6468c3`

Algorithm	Hash digest
SHA256	`13c8b013be599b619725cdbfef1bebaf7714c7667b52d140611e350635a35c64`
MD5	`6c60368566e22aef36b724d71eba6fa3`
BLAKE2b-256	`04c46381a697cb500c5d16bbbc0d72225f4edf8eda4b6e130d55f84ad00273d7`

Algorithm	Hash digest
SHA256	`b070517d52be33cdbb51c59e0e8fe4a5903be9d5ee81ea7c175721d1ccc38130`
MD5	`9826523df782e572f396f85e91b04efb`
BLAKE2b-256	`ca8dd865147ef3e00fad58b51fa168f1b00107ac5852b3bdd93cc53ba679240c`

Algorithm	Hash digest
SHA256	`21f9c01bf9a1288873d47ee796d4adc716aabf61b9b4061a13b8c7cc58b20dec`
MD5	`bf01d67daccea95d3586fab0afeb8c1c`
BLAKE2b-256	`a00ae85ef7dc57a7a1b69b8778271b61b3cd62f9a86612195d137a0110587a95`

Algorithm	Hash digest
SHA256	`02731defffea37879adcb420cab79303920744d57e16c7bd33df67a1cbdb78d2`
MD5	`f915996e5837d409c79f039aa64c2a9c`
BLAKE2b-256	`ea4529c2bfba3ab637b96565a21e0d422d18c6ccc980d7ef3d5cb2a691267da8`

Algorithm	Hash digest
SHA256	`993a102076b88c335ef9fb9dd85b49776258c68454ff79ce4740b5cc79be6ea2`
MD5	`d1cda1cc0b5967184852cf5a84c3a4aa`
BLAKE2b-256	`31c949f25692d2b23d103d4afde9d9a76fc3365e667db984ee48e877b36b6609`

Algorithm	Hash digest
SHA256	`9ffc90a0bd4e1e6f488b463360fa94bceabedd99e1ec9234a577064a1880ed7c`
MD5	`d1246cb460e82aa1dd7045864a819d9b`
BLAKE2b-256	`5fc54361e2e8332a9f92db3185facbc271c1b676d5abb2e2c4ab2fd11d7827b0`