From a783a10eb0698fac3d4be4348e4e751c649fdf80 Mon Sep 17 00:00:00 2001 From: Van Malleghem Antoine Date: Fri, 6 Sep 2024 19:53:08 +0200 Subject: [PATCH] fix README known issue Signed-off-by: Van Malleghem Antoine --- README.md | 25 +++++-------------------- 1 file changed, 5 insertions(+), 20 deletions(-) diff --git a/README.md b/README.md index 2920bc856c..6858c637be 100644 --- a/README.md +++ b/README.md @@ -99,29 +99,14 @@ gz sim -h In the event that the installation is a mix of Debian and from source, command line tools from `gz-tools` may not work correctly. -A workaround for a single package is to define the environment variable -`GZ_CONFIG_PATH` to point to the location of the Gazebo library installation, -where the YAML file for the package is found, such as +A workaround is to define the environment variable +`GZ_CONFIG_PATH` to point to the different locations of the Gazebo libraries installations, +where the YAML files for the packages are found, such as ``` -export GZ_CONFIG_PATH=/usr/local/share/gz +export GZ_CONFIG_PATH=/usr/local/share/gz:$HOME/ws/install/share/gz ``` -However, that environment variable only takes a single path, which means if the -installations from source are in different locations, only one can be specified. - -Another workaround for working with multiple Gazebo libraries on the command -line is using symbolic links to each library's YAML file. -``` -mkdir ~/.gz/tools/configs -p -cd ~/.gz/tools/configs/ -ln -s /usr/local/share/gz/fuel8.yaml . -ln -s /usr/local/share/gz/transport14.yaml . -ln -s /usr/local/share/gz/transportlog13.yaml . -... -export GZ_CONFIG_PATH=$HOME/.gz/tools/configs -``` - -This issue is tracked [here](https://github.com/gazebosim/gz-tools/issues/8). +where `$HOME/ws` is an example colcon workspace used to build Gazebo # Documentation