Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove need for ROS_messages redirected named-pipe #58

Merged
merged 1 commit into from
Jan 28, 2024

Conversation

gavanderhoorn
Copy link
Member

Turns out it's actually possible to directly open a named pipe, so we can do away with the redirect-named-pipe-to-file-in-mod-dir work-around.

Not sure why it works now, as from earlier tests we had the impression it didn't, but seeing as this simplifies things quite a bit, I'm not complaining.

See tud-cor/fs_mod_ros_windows#10 for the changes on the fs_mod_ros_windows side.

Turns out it's actually possible to directly open a named pipe, so we can do away with the redirect-named-pipe-to-file-in-mod-dir work-around.

Not sure why it works now, as from earlier tests we had the impression it didn't, but seeing as this simplifies things quite a bit, I'm not complaining.

Note: this also requires changes on the `fs_mod_ros_windows` side, but those will be made in that repository.
@gavanderhoorn
Copy link
Member Author

Merging as the CI failure is not related to this change.

@gavanderhoorn gavanderhoorn merged commit 519bf72 into tud-cor:master Jan 28, 2024
1 check failed
@gavanderhoorn gavanderhoorn deleted the direct_pipe_open branch January 28, 2024 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant