Conversation
Update
bf798cd to
1d61902
Compare
|
BTW @JanStaschulat are you ok with forcing the policy of the PR to be always "Squash and merge" instead of just "Merge" to avoid having a tree like this one: IMO in this image What do you think? |
|
Friendy ping @ralph-lange @JanStaschulat @norro |
|
"Are you ok with including this functionality as part of the RCLC library?" @pablogs9 thanks for creating a file for the sleep function. Ralph suggested to create a pull request to Before merging, though, @norro please fix the error in rclc_lifecycle for rolling or create another issue, in which you resolve this. |
|
#66 is the fix. |
@JanStaschulat These errors are fixed separately with #66 |
|
"BTW @JanStaschulat are you ok with forcing the policy of the PR to be always "Squash and merge" instead of just "Merge" to avoid having a tree like this one:" Yes, I agree. 'squash and merge' could be the default option. |
provide compatability for sleep function in Windows- and POSIX- operating systems.
provide compatability for sleep function in Windows- and POSIX- operating systems. Signed-off-by: Jan Staschulat <jan.staschulat@de.bosch.com>
provide compatability for sleep function in Windows- and POSIX- operating systems.
* Updated changelog, version 0.1.6 Signed-off-by: Jan Staschulat <jan.staschulat@de.bosch.com> * corrected changelog of rclc Signed-off-by: Jan Staschulat <jan.staschulat@de.bosch.com> * increased version in package.xml files Signed-off-by: Jan Staschulat <jan.staschulat@de.bosch.com>


I have had some incompatibility problems because we are forcing users to
#include <unistd.h>inexecutor.hand in some cross-compiled environments, this POSIX include is causing incompatibility errors.Are you ok with including this functionality as part of the RCLC library?