-
Notifications
You must be signed in to change notification settings - Fork 131
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
Enable basic warnings + include correct headers + remove Travis CI #148
Conversation
Signed-off-by: Audrow Nash <audrow.nash@gmail.com>
Signed-off-by: Audrow Nash <audrow.nash@gmail.com>
Signed-off-by: Audrow Nash <audrow.nash@gmail.com>
Signed-off-by: Audrow Nash <audrow.nash@gmail.com>
This reverts commit 9a4d55d.
This reverts commit 542110f.
Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
Signed-off-by: Audrow Nash <audrow.nash@gmail.com>
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.
add_library(urdfdom_world SHARED | ||
src/pose.cpp | ||
src/model.cpp | ||
src/link.cpp | ||
src/joint.cpp | ||
src/world.cpp) | ||
target_include_directories(urdfdom_world PUBLIC | ||
target_include_directories(urdfdom_world SYSTEM PUBLIC |
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.
this SYSTEM
keyword is applied not only to TinyXML_INCLUDE_DIRS
, but also to $<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/include>
and $<INSTALL_INTERFACE:include>
. is that ok? would it be better to split into separate calls to target_include_directories
, one with SYSTEM
and one without?
I don't know enough about how this works
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.
this
SYSTEM
keyword is applied not only toTinyXML_INCLUDE_DIRS
, but also to$<BUILD_INTERFACE:${CMAKE_CURRENT_SOURCE_DIR}/include>
and$<INSTALL_INTERFACE:include>
. is that ok? would it be better to split into separate calls totarget_include_directories
, one withSYSTEM
and one without?
I think that would work. @audrow can you give that a shot?
the travis-ci build can't find |
Yeah, travis isn't going to work on the |
👍 |
What is the strategy regarding the GitHub releases for this repo? If future 2.* release of this repo will be tagged/released on the |
It's a good question, and one that I've been pondering as well. In short, I don't know. The original goal here was to bring https://github.com/ros2/urdfdom back into this repository so we can have less divergence. As it stands, any PR against the Two ways to resolve this conflict that come to mind:
There may be other ways to handle it that I'm not thinking of. Regardless, I don't think this should hold up this particular PR. My suggestion to move forward here (and with #146) is to remove travis for now. Once we decide on a strategy going forward, we can reenable travis if we want. |
you could also have a cmake option 'USE_ROS_VENDOR'? |
Yeah, that's another way to do it. In order to play nicely in the ROS 2 builds, it would have to be enabled by default, and then downstreams could do |
The |
fyi I guess that @j-rivero as the Debian urdfdom maintainer could be interested in this discussion. |
While I think |
Just to be clear; this situation already exists today. The only difference is that it is now more visible since I merged the ros2 code into here. And to be further clear; if we went the route of having a I personally like that idea the best, though I'm not yet 100% convinced it will work in practice. |
I totally agree, but to clarify what I meant: as a downstream packager of urdfdom, from my point of view the ros2/urdfdom fork or the |
Actually I just noticed that tags such as https://github.com/ros/urdfdom/tree/2.3.3 are now present in the repo, so I would say that the problem emerged as those tags were added to this repo. |
@sloretz had another idea, which is to just switch those calls to |
Both this and the |
@clalancette, will do. |
Signed-off-by: Audrow Nash <audrow.nash@gmail.com>
Signed-off-by: Audrow Nash <audrow.nash@gmail.com>
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.
Looks good with green CI.
@clalancette or @scpeters, could you merge this PR in? I don't have permissions to. Also, I believe that ros2/urdfdom can be archived now. |
Woohoo, green CI! I'll wait for final approval from @scpeters before merging. |
This PR is a continuation of ros2#22 and enables
-Wall
,-Wextra
,-Wpedantic
. It should also fix #147.