You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Install ign-tools from debs: sudo apt install libignition-tools-dev
Build another library from source, such as ign-msgs.
Try to run ign msg, and ign-tools won't be able to find the msg 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, because IGN_CONFIG_PATH only accepts a single path.
Another workaround is to use symlinks as described here, for example:
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: