-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rosrust_msg does not automatically discover all msg files in package #166
Comments
I've been trying to parse the cmake macro definitions for |
For some additional info, when I try to manually add the messages, the proc-macro panics:
It's unclear from that message if it recurses into those directories to search, but the appropriate full path would have been It seems like it would be useful to have an additional macro option |
I've made a small re-implementation of the It seems like it'd make sense in the current build.rs paradigm to make use of Alternatively, the genmsg crate has a defined mechanism of passing in relevant information and generating msg and srv types. It'd be great to leverage the official mechanism here: https://github.com/ros/genmsg/blob/kinetic-devel/doc/developer.rst |
I have a catkin-based ROS1 project with a package
my_msgs
. The package contains msg and action definitions in a hierarchy like:With CMakeLists.txt declaring them like so:
After building, I try to execute
cargo build
on my rosrust binary crate that usesrosrust_msg
. It does generate some messages, but not all that I'm expecting so I looked into thebuild.rs
to do some debugging.It looks like the expected location for local package msg definitions is under
${CATKIN_WS}/devel/share/<package-name>/msg
and it's there that I find the generated msg files forMyAction.action
. These have types generated for them under therosrust_msg
package. However, there are no message files copied here for the other msg definitions. It seems like the discovery mechanism is incomplete here. I'd note thatrosmsg show
can find the message file definitions as it searches the src directory as well. It may be necessary to include that in order to do complete discovery.The text was updated successfully, but these errors were encountered: