-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
On Windows Gazebo does not start in Powershell or Git Bash #42
Comments
In https:/wolfv/multisheller/pull/8 I added support in multisheller to add and remove values from env variables list, that could be useful for this. Example of their use can be found for example in the files in https:/traversaro/robotology-superbuild/tree/6199a7d9e67de85d5c9024905f687f094ad37e8c/conda/multisheller, while the snippet of code to generate the actual scripts from the msh files can be found in https:/traversaro/robotology-superbuild/blob/6199a7d9e67de85d5c9024905f687f094ad37e8c/conda/python/generate_conda_recipes_from_metadatadata.py#L57 . |
At the moment gazebo on Windows does not start correctly in Powershell or Git Bash, and it works correctly only when launched on Command Prompt. I am not sure if this is expected or not, but having an issue open at least can be helpful for confused users.
In both Powershell and Git Bash, the error is the following:
This is probably caused by the fact that the activation script is running only when the activated bash is Command Prompt. The easiest solution for this may be to roll our our own https:/wolfv/multisheller scripts instead of relying on the one provided by Gazebo.
Environment (
conda list
):Details about
conda
and system (conda info
):The text was updated successfully, but these errors were encountered: