Skip to content
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

Add parameter to force Ignition Version #128

Merged
merged 1 commit into from
Mar 8, 2022

Conversation

luca-della-vedova
Copy link
Member

New feature implementation

Implemented feature

This PR adds a parameter to force the Ignition Gazebo version when running rmf_demos_ign launch files.

Implementation description

The plugins in rmf_simulation are compiled against a specific version of Ignition Gazebo and if a different version of Ignition than the one used to compile the plugins was to be ran, the simulation would crash.
By default, the ign gazebo CLI runs the most recent version of Gazebo, hence if a user was to install a newer version than the one supported demos would stop working.

This PR introduces a ignition_version parameter to rmf_demos_ign that defaults to the version plugins are built against. Since it specifies Fortress it should be merged together with open-rmf/rmf_simulation#70 to complete our migration. Users who wish to use different Ignition version can change the parameter value by doing, for example:

ros2 launch rmf_demos_ign office.launch.xml ignition_version:=6

Signed-off-by: Luca Della Vedova <luca@openrobotics.org>
Copy link
Member

@aaronchongth aaronchongth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding this support!

@aaronchongth aaronchongth merged commit 65c45a1 into main Mar 8, 2022
@aaronchongth aaronchongth deleted the feature/specify_ignition_version branch March 8, 2022 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants