-
Notifications
You must be signed in to change notification settings - Fork 129
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
Installing Gazebo11 side by side with new Gazebo Tutorial #438
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
# Installing Gazebo11 side by side with new Gazebo | ||
|
||
## Supported Gazebo versions and Ubuntu platforms for this tutorial | ||
|
||
This tutorial affects the Gazebo Classic users on Ubuntu `Jammy` (latest | ||
Ubuntu release were Gazebo Classic packages supported by the Gazebo team) | ||
that plan on migrating code to new Gazebo `Fortress`, `Garden` or `Harmonic.` | ||
|
||
There is no guarantee that the Gazebo Classic version detailed in this document | ||
will be updated in any case. Please consider the migration to the new Gazebo | ||
as the recommended alternative. | ||
|
||
## General context and migrations to new Gazebo | ||
|
||
New versions of Gazebo can not be installed together with Gazebo Classic | ||
(aka `gazebo11`) since both use the `gz` command line tool. Trying to | ||
install `gz-garden` or `gz-harmonic` from `packages.osrfoundation.org` | ||
on a system that already has gazebo-classic installed from binaries | ||
will cause gazebo-classic and its dependencies to be uninstalled. | ||
|
||
Having a side by side installation of both can make easier the recommended | ||
migration to newer versions of Gazebo. | ||
|
||
## Alternative approach for Gazebo Classic without the gz tool | ||
|
||
A possible workaround could be to use Gazebo Classic without the `gz` | ||
command or with a renamed `gz` command. This can be particularly | ||
interesting since the ROS (Robot Operative System) wrapper known as | ||
`gazebo_ros_pkgs` do not use the `gz` command but the `gzserver` and | ||
`gzclient` commands. | ||
|
||
Not shipping the `gz` command by default in a Gazebo Classic installation | ||
would be a disruptive change for existing users so it should not be hosted in | ||
`packages.osrfoundation.org`. | ||
|
||
## Gazebo11 with a separate gz tool package | ||
|
||
This alterntive approach has been implemented and packages for `jammy` are | ||
hosted in the Open Robotics `gazebo11-gz-cli` PPA: | ||
https://launchpad.net/~openrobotics/+archive/ubuntu/gazebo11-gz-cli | ||
|
||
The PPA contains a `gazebo11` version that ships the `gz` executable in | ||
an independent packages called `gazebo11-gz-cli` while the main `gazebo11` | ||
package has a `gz11` command. Both are really symlinks to `gz-11.x.y`. | ||
|
||
### How the packaging works for the gz command | ||
|
||
The `gazebo11-gz-cli` is a soft dependency on `gazebo11`. It is installed | ||
by default but it will be uninstalled when installing the new Gazebo | ||
packages and the effect is that the `gz` command for Gazebo Classic replaced | ||
by the `gz` tool from new Gazebo. The `gz11` command can be used instead of | ||
the `gz` command to access to the same functionality. | ||
|
||
## Installing the new packaging from the PPA | ||
|
||
From an existing `gazebo11` installation (on `jammy` the Ubuntu official | ||
repositories will install `11.10.2+dfsg-1` version) or a non existing | ||
`gazebo11` installation the steps are the following: | ||
|
||
```bash | ||
sudo add-apt-repository ppa:openrobotics/gazebo11-gz-cli | ||
sudo apt update | ||
sudo apt-get install gazebo11 | ||
``` | ||
|
||
If `gazebo11` was installed before, it will be upgraded to the version in the | ||
PPA. From this point, a new Gazebo installation for `fortress`, `garden` or | ||
`harmonic` can be executed. | ||
|
||
If a new Gazebo installation was installed before, the `gazebo11-gz-cli` package | ||
won't be installed. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@j-rivero This needs to 'index.yaml' to show up on the website