Introduced a conditional for mesh path inclusion #15
Conversation
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
As of writing this, gazebo_ros cannot handle the package://-syntax of mesh filenames. In order to work with gazebo, we'll have to rely on absolute paths. This will however destroy visualizing the description from a remote machine, as the absolute path there can (and most probably will) be different. This is considered a workaround until this issue is resolved upstream.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As of writing this, gazebo_ros cannot handle the package://-syntax
of mesh filenames. In order to work with gazebo, we'll have to rely
on absolute paths. This will however destroy visualizing the description
from a remote machine, as the absolute path there can (and most probably
will) be different.
This is considered a workaround until this issue is resolved upstream.
This is an alternative to #11 as discussed there.