ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A
Ask Your Question

Environment setup error - term 'call' is not recognized in PowerShell

asked 2020-03-26 08:19:57 -0600

Vuro H gravatar image

Hi, I am a ROS beginner installing ROS 2 on Windows and at the stage of sourcing the ROS 2 setup file to set up the workspace in PowerShell. However, when I enter the command call C:\dev\ros2_eloquent\local_setup.bat (which I have verified to be the correct directory), I receive the following error:

call : The term 'call' is not recognized as the name of a cmdlet, function,
script file, or operable program. Check the spelling of the name, or if a
path was included, verify that the path is correct and try again.
At line:1 char:1
+ call C:\dev\ros2_eloquent\local_setup.bat
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (call:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

What should I do to solve this? Thank you

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2020-03-26 11:44:29 -0600

Dirk Thomas gravatar image

These instructions are intended to be used with the cmd prompt.

If you want to use PowerShell you need to to invoke the setup file ending in .ps1 (which is the extension for PowerShell scripts).

edit flag offensive delete link more


Thanks a lot, works well in cmd. How do I invoke the setup file ending in .psl?

Vuro H gravatar image Vuro H  ( 2020-03-26 11:51:17 -0600 )edit

With just the filename.

Dirk Thomas gravatar image Dirk Thomas  ( 2020-03-26 11:59:31 -0600 )edit

thanks you a lot, it worked for me as well.

jimmy_hawkins gravatar image jimmy_hawkins  ( 2022-11-07 07:49:00 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools


Asked: 2020-03-26 08:19:57 -0600

Seen: 4,401 times

Last updated: Mar 26 '20