-
Notifications
You must be signed in to change notification settings - Fork 18
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
Too strict looking for config paths, difficult to combine different installs #8
Labels
bug
Something isn't working
Comments
multiple paths can now be specified in |
Ohh I think we can remove a bunch of troubleshooting sections then, like this one: https://github.com/ignitionrobotics/ign-fuel-tools/#known-issue-of-command-line-tools |
4 tasks
This was referenced Sep 23, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original report (archived issue) by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).
Prerequisites
Description
By default,
ign-tools
will look at its own installed path for yaml config files of other libraries. This works fine when all libraries have been installed from debs, because they all end up under the same directory structure under/usr
. But it fails for example when one was installed from debs and the other was installed from source to/usr/local
or some other custom path.Steps to Reproduce
ign-tools
from debs:sudo apt install libignition-tools-dev
ign-msgs
.ign msg
, andign-tools
won't be able to find themsg
command.Expected behavior:
Ignition tools should find the library, either by default, or with some documented configuration steps.
Actual behavior:
The command can't be found.
Additional Information
This discussion started on issue #2, look there for more context.
A partial solution is to set the
IGN_CONFIG_PATH
variable at runtime pointing at the library to be found. This works well if you only need to find libraries in a single path, but doesn't work for several libraries installed to different paths, becauseIGN_CONFIG_PATH
only accepts a single path.Another workaround is to use symlinks as described here, for example:
The text was updated successfully, but these errors were encountered: