Why is it that the binaries compiled in ros2_rust v0.5.1 or v0.6.1 depend on test_msgs? The official ROS definition for this library is for testing purposes, but in reality, it has become a runtime dependency for Rust. This is quite unreasonable. How can this be resolved?

[Kimhlo]

when we using ldd to show the denpendy lib：

libtest_msgs__rosidl_typesupport_c.so => xxxxxxxxx
libtest_msgs__rosidl_generator_c.so => xxxxxxxx

[mxgrey]

In order for rclrs to be published to crates.io we bundle up all the message bindings that it needs into the vendor module. test_msgs is used by tests, so the bindings are in there.

This is not an arrangement that we really want, but it seemed like the best compromise that we could come up with for now. We're very open to suggestions for other approaches.

For test_msgs in particular, since they're only used for testing, we might be able to wrap #[cfg(test)] around the module to prevent it from being included outside of tests.

[Kimhlo]

#[cfg(test)]
pub mod test_msgs;
it is works, thanks a lot, I don't need to change mine package anymore!