Skip to content

In Conda documentaton, document that the preferred shell on Windows is Command Prompt and that the environment should be as clean as possible #850

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Aug 7, 2021
Merged

In Conda documentaton, document that the preferred shell on Windows is Command Prompt and that the environment should be as clean as possible #850

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
81d05ae
In Conda documentaton, document that the preferred shell is Command P…
traversaro Aug 5, 2021
d40021e
Update conda-forge.md
traversaro Aug 5, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion doc/conda-forge.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,10 @@ conda activate robotologyenv

**IMPORTANT: if you open a new terminal, you need to manually activate the environment also there.**

**IMPORTANT: To avoid strange conflicts in environment variables, it is a good idea to remove from the environment any variable that refers to libraries or software not installed with conda. For example, if you have a robotology-superbuild installed with apt dependencies, it is a good idea to remove the source of the `setup.sh` from the `.bashrc` before using conda environments, or in Windows it can make sense to check with [Rapid Environment Editor](https://www.rapidee.com) that the environment is clean.**

**IMPORTANT: On Windows, it is recommended to use Command Prompt to manage conda environments, as some packages (see https://github.com/conda-forge/gazebo-feedstock/issues/42 and https://github.com/RoboStack/ros-noetic/issues/21) have problems in activating environments on Powershell.**

### Install robotology packages

Once you are in an activated environment, you can install robotology packages by just running the command:
Expand Down Expand Up @@ -103,7 +107,11 @@ conda activate robsub
~~~

**IMPORTANT: if you open a new terminal, you need to manually activate the environment also there. If you compiled a robotology-superbuild in a given conda environment, remember to activate it before trying to compile or run any package
of the robotology-superbuild.**
of the robotology-superbuild.**

**IMPORTANT: To avoid strange conflicts in environment variables, it is a good idea to remove from the environment any variable that refers to libraries or software not installed with conda. For example, if you have a robotology-superbuild installed with apt dependencies, it is a good idea to remove the source of the `setup.sh` from the `.bashrc` before using conda environments, or in Windows it can make sense to check with [Rapid Environment Editor](https://www.rapidee.com) that the environment is clean.**

**IMPORTANT: On Windows, it is recommended to use Command Prompt to manage conda environments, as some packages (see https://github.com/conda-forge/gazebo-feedstock/issues/42 and https://github.com/RoboStack/ros-noetic/issues/21) have problems in activating environments on Powershell.**

Once you activated it, you can install packages in it. In particular the dependencies for the robotology-superbuild can be installed as:
~~~
Expand Down