Universal_Robots_ROS2_Driver icon indicating copy to clipboard operation
Universal_Robots_ROS2_Driver copied to clipboard

Invalid path in git

Open michaelaeriksen opened this issue 3 years ago • 8 comments

When checking out this repo I get

OS: Windows

error: invalid path 'ur_robot_driver/resources/ursim_driver/ursim/aux/.vol/urcap_ros_control.installation'

Note: The ROS1 version of these driver do not have this issue.

michaelaeriksen avatar Dec 02 '21 17:12 michaelaeriksen

@michaelaeriksen Thanks for your question. I am not really sure why windows is not happy with that filename, but thanks for the insight Maybe you can get going with Windows Subsystem for Linux (WSL).

Please note that the driver does not yet support Windows natively.

urrsk avatar Dec 03 '21 11:12 urrsk

I forked the Universal_Robots_ROS2_Driver repo and used wsl to remove the files giving me problems in Windows. I have the ROS version of the drivers working on Windows natively and I'm now looking at migrating to ROS2. A while back I forked the Universal_Robots_Client_Library repo and changed all the socket code to use the platform independent asio library and the ROS version of the drivers are working great.

michaelaeriksen avatar Dec 03 '21 15:12 michaelaeriksen

@michaelaeriksen that sounds great. Have you any idea of why windows did not like that file? We have talked about making the ROS2 driver windows compatible, and here you work sounds very interesting. Is it possible for you to share the asio version?

urrsk avatar Dec 07 '21 11:12 urrsk

aux seems to be a reserved filename on windows. We ran into this issue before and renaming the path worked for us!

https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN

relffok avatar Apr 21 '22 09:04 relffok

aux seems to be a reserved filename on windows. We ran into this issue before and renaming the path worked for us!

https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN

Thanks for that insight!

fmauch avatar Apr 21 '22 09:04 fmauch

How did you workaround this? Did you fork and rename?

haellingsen avatar Sep 21 '22 07:09 haellingsen

@haellingsen you could use the branch from #478 for example. This will see some more work today, but the problematic folder is already removed.

fmauch avatar Sep 21 '22 08:09 fmauch

@haellingsen you could use the branch from #478 for example. This will see some more work today, but the problematic folder is already removed.

Thanks.

Although I ran git config core.protectNTFS false and cloned it.

appselskapet avatar Sep 21 '22 08:09 appselskapet

Since the path is no longer part of the main branch, I'm going to close this.

fmauch avatar May 09 '23 06:05 fmauch