chore: update hardware interface #25
Conversation
Signed-off-by: wep21 <[email protected]>
Signed-off-by: wep21 <[email protected]>
|
It is not obvious to me if the ABI is changed or not in hardware_interface ( ros-controls/ros2_control@4.23.0...4.25.0 ). Can you include the needed changes as patches instead of bumping the version, so it is easier to check if they are ABI compatible? |
| $<BUILD_INTERFACE:${PROJECT_SOURCE_DIR}/include> | ||
| $<INSTALL_INTERFACE:include/hardware_interface> | ||
| ) | ||
| +target_link_libraries(mock_components PUBLIC hardware_interface) |
There was a problem hiding this comment.
ros-controls/ros2_control#1992
already fixed
|
@traversaro In the latest jazzy sync, ros2 control is updated from 4.23 to 4.25 and ros2 control maintainers release the master branch as jazzy which may break abi compatibility. How can we treat it? |
If there is an update that breaks ABI, we can only do that as part of a full rebuild (that is essentially the robostack equivalent of the bloom sync). |
|
I see. I close this PR, once. |
2 participants
No description provided.