Conversation
|
Now we get a meaningful error w.r.t. pkg-config: |
|
I'll run again with pkg-config installed, the deb should be updated to depend on it. I think @esteve may already be away of that since we talked about it this morning. |
|
New problem: http://54.183.26.131:8080/job/ros2_batch_ci_test_linux/32/console It doesn't find all of the required libraries. That job is with the four rti binaries (excluding the rti tools deb), NDDS_HOME is not set, pkg-config is explicitly installed, and this pull request's branch is being used. |
…ing51-dev >= 5.1.0-3
|
The ros2_batch_ci_linux job now finds RTI Connext: http://54.183.26.131:8080/view/ros2/job/ros2_batch_ci_linux/15/console |
|
@dirk-thomas @tfoote @wjwwood please review |
|
+1 |
There was a problem hiding this comment.
Why does this not contain nddscpp_LIBRARIES anymore?
There was a problem hiding this comment.
Because rticonnextmsgcpp_LIBRARIES already contains them.
There was a problem hiding this comment.
If rticonnextmsgcpp contains the superset of nddscpp as well as the messaging libraries should we then just find_package(rticonnextmsgcpp) and use its variables? The mixture looks weird to me.
There was a problem hiding this comment.
We could add nddscpp_LIBRARIES, even if it's a bit redundant, and remove them from here when/if the messaging libraries are included in RTI Connext.
There was a problem hiding this comment.
The PR can be merged as-is but this should be cleaned up sometime in the near future (if we don't a Connext version which just solves that in a single package).
There was a problem hiding this comment.
I agree that's weird that we find package both but use INCLUDE_DIRS from one and LIBRARIES from another. At the very least maybe @esteve could add a comment that rticonnextmsgcpp_LIBRARIES contains the nddscpp_LIBRARIES and a TODO comment to clean it up?
There was a problem hiding this comment.
I ended up adding nddscpp_LIBRARIES too, it took less time than adding a comment :-)
|
So, are we going to make an adjustment to this or is it good to go? I don't mind either way, just wondering. |
|
+1 |
Look for the nddscpp CMake module
No description provided.