composite messages problem

[micmzr]

I would like to define my own message type, such as:

geometry_msgs/Point[] waypoints

I add this to: rclrs_example_msgs/msg/VariousTypes.msg

Modifies files accordingly

rclrs_example_msgs/CMakeLists.txt
...
+find_package(geometry_msgs REQUIRED)

set(msg_files
"msg/NestedType.msg"
"msg/VariousTypes.msg"
"msg/MyMessage.idl"
+DEPENDENCIES geometry_msgs
)
...

rclrs_example_msgs/package.xml
...
+geometry_msgs
...

The rclrs_example_msgs package compiles fine, but examples_rclrs_message_demo doesn't compile:
--> /home/mmazur/Projekty/examples/install/rclrs_example_msgs/share/rclrs_example_msgs/rust/src/msg.rs:480:24
|
480 | pub waypoints: Vec<geometry_msgs::msg::Point>,
| ^^^^^^^^^^^^^ use of unresolved module or unlinked crate geometry_msgs
|
= help: if you wanted to use a crate named geometry_msgs, use cargo add geometry_msgs to add it to your Cargo.toml

What can I do?
I haven't had problems with composite messages before.

[azerupi]

Just checking, did you also add the dependency to your Cargo.toml in addition to your package.xml? The package.xml tells colcon (in this case colocon-ros-cargo) which package needs to be built that you depend on but then since the Rust crates are built with Cargo, Cargo also needs to know about that crate. If you haven't done it, you need to depend on geometry_msgs in your Cargo.toml by adding this in your Cargo.toml

geometry_msgs = "*"

[micmzr]

If I do this I will get the following error:
error: failed to select a version for the requirement geometry_msgs = "*"
version 4.2.3 is yanked

I suppose the idea is to use ros_env now. It's a shame that the appropriate crates aren't available, as it breaks compatibility with old code.

[azerupi]

Yes, moving to ros_env is the right path forward.
Although depending on your ROS 2 distro, the old workflow should still work until a sync happens which would rebuild the apt message packages. So far this has only happened on kilted and lyrical I believe. But to future proof your projects, I would recommend moving to use ros_env because your packages would break on the next sync anyway.

If you are not on kilted or lyrical, then something might be wrong with your setup because then I would expect the message packages to be patched in the <ros_ws>/.cargo/config.toml file.

[micmzr]

I am using lyrical and ros_env.

[micmzr]

After

rm -rf build/ install/ .cargo

everything compiled correctly.
Something seems to be failing to update after adding new message types.