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
We currently only support looking up config files by absolute paths, or paths relative to the running directory. It would be convenient for downstream packages if users could reference their installed configs without knowing the full path.
Desired behavior
A package installs several config files in, for example, install/share/package_name/gui_config
Then it sets the IGN_GUI_CONFIG_PATH variable to that folder
At runtime, users can load those config files from the command line with ign gui -c filename.config or ign gazebo --gui-config filename.config
Alternatives considered
We usually use environment variables for this kind of lookup path. One thing to consider is to have a generic path, such as IGN_GUI_RESOURCES, that can be reused for things other than config files.
Implementation suggestion
Look at how IGN_GAZEBO_RESOURCE_PATH is implemented, for example.
The text was updated successfully, but these errors were encountered:
We currently only support looking up config files by absolute paths, or paths relative to the running directory. It would be convenient for downstream packages if users could reference their installed configs without knowing the full path.
Desired behavior
install/share/package_name/gui_config
IGN_GUI_CONFIG_PATH
variable to that folderign gui -c filename.config
orign gazebo --gui-config filename.config
Alternatives considered
We usually use environment variables for this kind of lookup path. One thing to consider is to have a generic path, such as
IGN_GUI_RESOURCES
, that can be reused for things other than config files.Implementation suggestion
Look at how
IGN_GAZEBO_RESOURCE_PATH
is implemented, for example.The text was updated successfully, but these errors were encountered: