rosidl_runtime_rs differences between main and crate breaks colcon build

[texhnolyze]

rosidl_runtime_rs differences between main and crate breaks colcon build

[texhnolyze]

Ok while typing the answer I realized that you were talking about ~/.cargo/config.toml.
As colcon creates a bunch of files/folders I have its own folder as a workspace under ~/colcon_ws resulting in the patch configuration for the path of rosidl_runtime_rs ending up in ~/colcon_ws/.cargo/config.toml and not being applied.
Copying the file to the correct folder in the homedir fixes the issue.
I suppose in this case it is more an issue with colcon-ros-cargo?
Looking at the code it the .cargo/config.toml is place in the working directory https://github.com/colcon/colcon-ros-cargo/blob/main/colcon_ros_cargo/task/ament_cargo/build.py#L100.
So I guess it not working is maybe due to the execution directory of cargo in the colcon build, as according to the docs if it is executed in the working dir the configuration should be applied.
Unless passing --manifest-path or --target-dir here change that.

Anyway it seems to not be an issue with ros2_rust.
@nnmm I saw that you are also maintaining colcon-ros-cargo.
I'm happy to open an issue there and do a PR if you could point me in the right direction.

[texhnolyze]

After a quick search, this might even be just a bug in cargo itself rust-lang/cargo#2930

[nnmm]

Thanks for the report! I'm trying to understand how the two versions got mixed – could you tell me how you depend on rclrs in your project (i.e. do you have a checkout of the repo, or through crates.io? And how is rclrs referenced in your Cargo.toml?)? And what is listed for rclrs and rosidl_runtime_rs in ~/.cargo/config.toml?