Closed ChrisTimperley closed 5 years ago
Issue is avoided by switching from Indigo to Kinetic. Bug is not dependent on a particular ROS version.
Issue is avoided by switching from Indigo to Kinetic. Bug is not dependent on a particular ROS version.
isn't that a contradiction?
If the bug isn't dependent on a particular ROS version, how can switching from one to the other have such an affect as to make the build succeed?
Issue is avoided by switching from Indigo to Kinetic. Bug is not dependent on a particular ROS version.
isn't that a contradiction?
If the bug isn't dependent on a particular ROS version, how can switching from one to the other have such an affect as to make the build succeed?
Because the Indigo versions of libmavconn
do not provide support for v2.0 of the mavlink
protocol. Support for mavlink
v2.0, which is required to build the PUT, was added in Kinetic.
So then it is dependent on a particular ROS distribution.
So then it is dependent on a particular ROS distribution.
The bug, described in the .bug
file (please read: https://github.com/robust-rosin/robust/blob/master/mavros/1a746c3/1a746c3.bug), is not related to a particular version of ROS.
Misunderstood "the bug" here in this case.