Crates.io | roslibrust_codegen_macro |
lib.rs | roslibrust_codegen_macro |
version | |
source | src |
created_at | 2022-08-28 20:57:47.505509+00 |
updated_at | 2025-04-07 18:45:08.071399+00 |
description | Provides macro-based message generation for roslibrust |
homepage | |
repository | https://github.com/Carter12s/roslibrust |
max_upload_size | |
id | 654066 |
Cargo.toml error: | TOML parse error at line 21, column 1 | 21 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
This crate defines the proc-macro for generating ROS message types. It invokes APIs from the roslibrust_codegen
crate.
This macro cannot detect if the message files it generates from have changed. If you are creating a crate which just contains your message definitions and won't be recompiled otherwise, you'll likely want to use roslibrust_codegen
with a build.rs
script.
If you're generating messages in an environment with ROS installed, no arguments need to be passed.
use roslibrust_codegen_macro::find_and_generate_ros_messages;
find_and_generate_ros_messages!();
If you're generating without ROS installed or your environment can't depend on the ROS_PACKAGE_PATH
variable, you can specify additional paths to search:
use roslibrust_codegen_macro::find_and_generate_ros_messages;
find_and_generate_ros_messages!("/path/to/my/msg/package", "/opt/ros/noetic");