-
Notifications
You must be signed in to change notification settings - Fork 486
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
Update TinyOBJLoader to v2.0.0rc8 #2885
Conversation
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.
Did not find anything wrong in the PR or in the TinyOBJLoader bump. We can update changelog in this PR (unless you plan to update it with the changes for making the files with spaces to work):
diff --git a/Changelog.md b/Changelog.md
index 37a5d4c38a..cb80e23f18 100644
--- a/Changelog.md
+++ b/Changelog.md
@@ -5,6 +5,9 @@
1. Fix physics based sensor update rate in lockstep mode
* [Pull request #2863](https://github.com/osrf/gazebo/pull/2863)
+1. Updated the version of TinyOBJLoader from 1.0.0 to 2.0.0rc8.
+ * [Pull request #2885](https://github.com/osrf/gazebo/pull/2885)
+
## Gazebo 9.15.0 (2020-09-30)
1. More enhancement for Windows build
I'm compiling the beast to give it a quick try before approve it.
Signed-off-by: Louise Poubel <louise@openrobotics.org>
763da38
to
c81e2d9
Compare
No problem. I did not find any problem on the runtime manual test. All the failing tests seems not related to the ones involved in this PR, specially factory and obj_loader. Nice work. |
Signed-off-by: Louise Poubel <louise@openrobotics.org>
Signed-off-by: Louise Poubel <louise@openrobotics.org>
Builds on top of #2877, resolves #2870.
This completes the support of files containing white spaces. The support for referring to MTL files with spaces from OBJ files has been added to TinyOBJLoader on tinyobjloader/tinyobjloader#285 and is staged to be released into their 2.0.0 version.
I don't think it's a great idea to use a release candidate, but it looks like the
v2.0.0rc8
tag doesn't break any of our existing use cases and brings lots of new features.The only API change from the revision we were previously using was the addition of warning messages, and that was added back in
v1.3.0
, so it's not an artifact of bumping the major version.