Comments (10)
You need to clone geometry_msgs
into your workspace. std_msgs
is already cloned by the vcs import src < src/ros2_rust/ros2_rust_foxy.repos
step.
from ros2_rust.
Shouldnt geometry_msg
also be cloned alongside with std_msgs
?
Since both are from url: https://github.com/ros2/common_interfaces.git
, which is in vcs import src < src/ros2_rust/ros2_rust_foxy.repos
You might as well give some instructions too
from ros2_rust.
Oh, you're right.
Did you add geometry_msgs
to package.xml
of your package? Are you building with colcon
or cargo
?
from ros2_rust.
I tried both via colcon and cargo.
And I've added geometry_msg to package.xml
from ros2_rust.
Ok. When you build with colcon
, does it say that it's building geometry_msgs
? And is geometry_msgs
mentioned in your .cargo/config.toml
file afterwards?
from ros2_rust.
Oh, I havent noticed this before.
It does say that it finished building Finished <<< geometry_msgs [2.01s]
, when I did colcon build
, but I get the cargo build
error nonetheless.
Starting >>> turtle_rust
--- stderr: turtle_rust
error: failed to compile `turtle_rust v0.1.0 (/home/us/turtlebot3_ws/src/turtle_rust)`, intermediate artifacts can be found at `/home/us/turtlebot3_ws/src/turtle_rust/target`
Caused by:
no matching package named `geometry_msgs` found
location searched: registry `crates-io`
required by package `turtle_rust v0.1.0 (/home/us/turtlebot3_ws/src/turtle_rust)`
---
Failed <<< turtle_rust [0.83s, exited with code 101]
Heres the .cargo/config.toml
:
[patch.crates-io.test_msgs]
path = "/home/us/turtlebot3_ws/install/test_msgs/share/test_msgs/rust"
[patch.crates-io.action_msgs]
path = "/home/us/turtlebot3_ws/install/action_msgs/share/action_msgs/rust"
[patch.crates-io.unique_identifier_msgs]
path = "/home/us/turtlebot3_ws/install/unique_identifier_msgs/share/unique_identifier_msgs/rust"
[patch.crates-io.builtin_interfaces]
path = "/home/us/turtlebot3_ws/install/builtin_interfaces/share/builtin_interfaces/rust"
[patch.crates-io.rclrs]
path = "/home/us/turtlebot3_ws/install/rclrs/share/rclrs/rust"
[patch.crates-io.rosidl_runtime_rs]
path = "/home/us/turtlebot3_ws/install/rosidl_runtime_rs/share/rosidl_runtime_rs/rust"
[patch.crates-io.turtlebot3_msgs]
path = "/home/us/turtlebot3_ws/install/turtlebot3_msgs/share/turtlebot3_msgs/rust"
[patch.crates-io.dynamixel_sdk_custom_interfaces]
path = "/home/us/turtlebot3_ws/install/dynamixel_sdk_custom_interfaces/share/dynamixel_sdk_custom_interfaces/rust"
[patch.crates-io.example_interfaces]
path = "/home/us/turtlebot3_ws/install/example_interfaces/share/example_interfaces/rust"
[patch.crates-io.std_msgs]
path = "/home/us/turtlebot3_ws/install/std_msgs/share/std_msgs/rust"
[patch.crates-io.rclrs_example_msgs]
path = "/home/us/turtlebot3_ws/install/rclrs_example_msgs/share/rclrs_example_msgs/rust"
package.xml
:
<package format="3">
<name>turtle_rust</name>
<version>0.0.0</version>
<description>TODO: Package description</description>
<maintainer email="[email protected]">user</maintainer>
<license>TODO: License declaration</license>
<depend>rclrs</depend>
<depend>std_msgs</depend>
<depend>geometry_msgs</depend>
<export>
<build_type>ament_cargo</build_type>
</export>
</package>
from ros2_rust.
Very strange. Do you have a repo somewhere that I could clone to reproduce this behavior?
from ros2_rust.
I do not I'll just say what I did, maybe it's something very "silly". If it can't be seen, I'll just upload it on GitHub.
mkdir -p workspace/src && cd workspace
git clone https://github.com/ros2-rust/ros2_rust.git src/ros2_rust
vcs import src < src/ros2_rust/ros2_rust_foxy.repos
. /opt/ros/foxy/setup.sh
colcon build
cd src
~/workspace/src$ cargo new republisher_node && cd republisher_node
~/workspace/src/republisher_node/Cargo.toml
:
[package]
name = "republisher_node"
version = "0.1.0"
edition = "2021"
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies]
rclrs = "*"
std_msgs = "*"
Create a new ~/workspace/src/republisher_node/package.xml
:
<package format="3">
<name>republisher_node</name>
<version>0.0.0</version>
<description>TODO: Package description</description>
<maintainer email="[email protected]">user</maintainer>
<license>TODO: License declaration</license>
<depend>rclrs</depend>
<depend>std_msgs</depend>
<export>
<build_type>ament_cargo</build_type>
</export>
</package>
-
~/workspace$ colcon build
==> Success -
Update
cargo.toml
by addinggeometry_msgs = "*"
under[dependencies]
: -
Add
<depend>geometry_msgs</depend>
in~/workspace/src/republisher_node/package.xml
: -
(catkin clean) :
~/workspace$ rm -r build install log
-
~/workspace$ colcon build
EDIT: Works now after typo fix
--- stderr: republisher_node
error: no matching package named geometry_msg
found
location searched: registry crates-io
required by package `republisher_node v0.1.0
EDIT: Fixed spelling error geometry_msg
to geometry_msgs
, after closing.
from ros2_rust.
13. geometry_msg
The name of the package is geometry_msgs
, in plural.
from ros2_rust.
Oh yeah, its working now !
Dont know where I went wrong the first time , since I had geometry_msgs
.
I'll just continue with this new one.
Thanks!
from ros2_rust.
Related Issues (20)
- Zero copy publisher example fails HOT 1
- `extern` block uses type `u128`, which is not FFI-safe HOT 7
- support `rclrs::SerializedMessage`
- compile failed when deserilize msg struct
- Improve support for rust analyzers
- Fix documentation now that rclrs is on crates.io
- Does it make sense to publish Docker images? HOT 2
- Docs Fail to Generate on Docs.rs HOT 3
- Barebone Compile of Repository Fails HOT 3
- 0.4 Release Tracking Issue HOT 5
- does ros2_rust support autogeneration of code from .idl and .msg files, is there any example implementation to autogenerate rust nodes from .idl/.msg files? HOT 1
- A small tool for creating ros2 rust packages is available. HOT 3
- Build Error: unable to find std_msgs HOT 1
- Support for Bevy HOT 7
- Investigate Release Builds with Debug Symbols under GDB for potential issues with rclrs_tests usage of DDS HOT 2
- Attempt to reproduce intermittent unit test failures with a different DDS vendor HOT 1
- Check if our CI configuration is potentially causing our intermittent failures HOT 1
- Move rclrs_test into rclrs
- Investigate the rcl struct drop order HOT 4
- Failed to build depends on `builtin_interfaces` HOT 10
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ros2_rust.