jhdcs
jhdcs
The changes look good, and we have a passing CI! Thank you very much for your help! Merging...
The problem is that no matter what, the interaction between `colcon` and `cargo` has _always_ forced us to make unconventional approaches. They're both opinionated systems, and it feels like their...
I like avoiding needing to vendorize messages. That should hopefully make things a bit easier on the end user as well...
I'm not seeing anything on passing arbitrary metadata to a dependency, but I'll try to keep looking...
I don't suppose the `pkg-config` crate would be useful for this? https://crates.io/crates/pkg-config
Glad I could help! For extra info, I bumped into that package while browsing through the official Build Script Examples page: https://doc.rust-lang.org/cargo/reference/build-script-examples.html
I like the idea of reading the dependencies from the `package.xml` if possible. Not sure how much more difficult that would be, though.
I think one of the difficulties of deriving traits for message types is that we have very little information about the individual messages before compile time. We cannot be sure...
I like the idea of a client builder. Rust does like its builder patterns, after all.
#380 has been merged in. @sprhawk, would you be able to try this again and let us know if the issue is resolved?