-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
ROS tools not found in PowerShell on Windows #21
Comments
See conda-forge/gazebo-feedstock#42 for a related issue .. /Cc @traversaro @wolfv |
Ah okay, sounds like there isn't a |
I don't really know what's needed to get this working. If you have an idea, please feel free to open a pull request - this would be a great addition 👍 |
Thanks for the quick replies, I'll try to help with this. |
Thanks for reporting the issue! The issue conda-forge/gazebo-feedstock#42 is related but it is not tracking the same problem as gazebo is a standalone conda-forge recipe that it is not related to the ROS packages generated on the |
Thanks for the info @traversaro. On Gitter, I've seen mention of multisheller. Is it worth looking into that and if so, are there any examples of it being used here yet? |
I guess that in the ROS use case, |
Ah okay. Thanks for your help. |
I looked a bit into this, and from the vinca point of view, it should be sufficient to add the However, the problem for ROS1 is that catkin does not support at the moment generating PowerShell environment scripts (see https://github.com/ros/catkin/blob/203a57ad70430ae165ebe014738a37c3af3e9166/cmake/catkin_generate_environment.cmake#L102 for the supported shells), so for solving that we should either add this to catkin, or add it as a catkin patch. I also looked if there was some way of "sourcing" .bat scripts in powershell, but I could not find any. The nice thing is that instead on ROS2 ament_cmake/colcon already supports generating .ps1 environment scripts (see https://colcon.readthedocs.io/en/released/developer/environment.html#entry-points), so supporing PowerShell on ROS2 would be easier, as it would only require to modify vinca to generate the correct activation scripts. |
On Windows 10 x86 64bit, ROS tools like
roscore
,rostopic
, etc. all work fine with Command Prompt. But when I runroscore
with PowerShell, I see the following:rostopic
,rosservice
, and the others show similar ModuleNotFoundErrors.The text was updated successfully, but these errors were encountered: