-
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
Several ignition projects install the .yaml file even if the ruby script is not installed #71
Comments
I think both files should always be installed. For ign-plugin, there was a problem on windows, so the |
This requires generating the .rb and .yaml files to folders unique to $<CONFIG>. Part of gazebosim/gz-tools#71. Signed-off-by: Steve Peters <[email protected]>
fix for ign-plugin in gazebosim/gz-plugin#63 |
This requires generating the .rb and .yaml files to folders unique to $<CONFIG>. Part of gazebosim/gz-tools#71. Signed-off-by: Steve Peters <[email protected]>
This requires generating the .rb and .yaml files to folders unique to $<CONFIG>. Part of gazebosim/gz-tools#71. Signed-off-by: Steve Peters <[email protected]>
As part of gazebo-tooling/release-tools#472 we've been updating all libraries to always install the files needed by |
This will be fixed by gazebosim/gz-msgs#402 . |
Desired behavior
While debugging a related problem, I noticed that on a Windows installation of a Ignition Fortress,
ign --help
was printing this message:But then for several of this commands, the execution failed with with error like:
The problems seems that in many cases, even if the installation of the cmd<> ruby script is disable, the yaml file describing the ign-tool plugin is installed anyway.
This problem seems to affect the following repos:
Implementation suggestion
Probably for all this projects a single options should control the installation of both the
yaml
andrb
ign-tools-related files.Additional context
Even if strictly speaking this is not an ign-tools issue, I preferred to open an issue in ign-tools as the details of the issues affecting those repos are the same.
The text was updated successfully, but these errors were encountered: