-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Missing local_setup.ps1 on win-64 ros humble #108
Comments
As mentioned in the docs (in https://robostack.github.io/GettingStarted.html), powershell is not supported/tested at the moment, see RoboStack/ros-galactic#91 . Some work was done in RoboStack/vinca#34, but not tested in depth. I guess the issue is on the vinca/robostack side. |
Thanks for quick response @traversaro. I didn't really read that. I will try with cmd |
I really wanted the powershell to work with ros-galactic, so I tried to dig more info by reading the code. I looked at the sibling However, I downloaded the ros2 windows binary and found that the So, I think to have PowerShell working in Robostack, we should start integrating the colcon-powershell into the build process. The colcon-powershell looks promising as it also generate the prefix, per-package, and hook for powershell. |
Ah, great find! /cc @traversaro |
I guess one issue is that we use catkin/ament for building our packages, not colcon. So I'm not sure how it would work, we might need to change the build process potentially. |
The harder / better way would probably be to add templates for ament_package at https://github.com/ament/ament_package/tree/rolling/ament_package/template |
Solution to issue cannot be found in the documentation.
Issue
Getting the following error. Missing local_setup.ps1
For reference, I can see the
local_setup.bat
but notlocal_setup.ps1
. I think we need to find how the.ps1
is linked/created. Not sure if issue from robostack or from ros/ament.Reproduce steps:
Open new tab and then the error message above starts appearing.
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: