Question about handling Micro-CDR about embeddedrtps

[takasehideki]

@akampmann Thank you so much for answering my questions!
In my opinion, it can be tracked to the latest version in the following ways.

1. fork eProsima/Micro-CDR into your organization embedded-software-laboratory
2. remove the current embeddedRTPS/thirdparty/Micro-CDR directory
3. add 1. as the submodule
4. and then, checkout eProsima/Micro-CDR@62d95c8 (commit ID you copied)
5. track some commits you added for embeddedRTPS https://github.com/embedded-software-laboratory/embeddedRTPS/commits/master/thirdparty/Micro-CDR

I think the report from @pablogs9 is very useful. Thanks!
We can use the latest version of Micro-CDR in embeddedRTPS as it is just by importing pablogs9@7a8b9a4

---

FYI: We decided to fix the issue of name conflict about #include <ucdr/types/string.h> that happened to support Mbed Web Compiler by changing the filename. Please check mROS-base#6
But we would be happy if you could track the latest version of Micro-CDR.

[akampmann]

This branch contains the latest Micro-CDR release as a submodule and the changes suggested by @pablogs9

https://github.com/embedded-software-laboratory/embeddedRTPS/tree/feature/microcdr-submodule

Could you check if this works for you? Its compiling on my side, but will take a few days to run it on target platform for me.

[akampmann]

Edit: We should definitely track the latest Micro-CDR if possible, we just have to figure out how to do this best.

Q1: I should be somewhere around this commit: eProsima/Micro-CDR@62d95c8

Q2: I absolutely don't mind adding Micro-CDR as a submodule. embeddedRTPS is currently used for a non-public project, where Micro-CDR is also used. Currently, the versions between embeddedRTPS and that other project match. I will have to double check what the necessary changes to the latest Micro-CDR project are. Does mROS itself also require changes to the latest Micro-CDR?

[pablogs9]

In micro-ROS we are using embeddedRTPS with mainline Micro-CDR. In this case, just using them as a CMake dependency managed with colcon. But I found a couple of problems when using latest version of our library. Maybe this commit can clarify something: pablogs9@7a8b9a4

[akampmann]

Thank you both for your suggestions. I will have a look and come back about this.