From 2b02f9b83f91a8d9445411d0c8f036582be61c6b Mon Sep 17 00:00:00 2001 From: Van Malleghem Antoine Date: Wed, 4 Sep 2024 17:57:39 +0200 Subject: [PATCH] fix-readme-known-issue Signed-off-by: Van Malleghem Antoine --- README.md | 25 ++++--------------------- 1 file changed, 4 insertions(+), 21 deletions(-) diff --git a/README.md b/README.md index 1ce861b..810069a 100644 --- a/README.md +++ b/README.md @@ -71,30 +71,13 @@ Sample launch configuration files are in the [examples directory](https://github 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/.gz/tools/configs ``` -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/fuel4.yaml . -ln -s /usr/local/share/gz/transport7.yaml . -ln -s /usr/local/share/gz/transportlog7.yaml . -... -export GZ_CONFIG_PATH=$HOME/.gz/tools/configs -``` - -This issue is tracked [here](https://github.com/gazebosim/gz-tools/issues/8). - # Documentation See the [installation tutorial](https://gazebosim.org/api/launch/8/install.html).