rosdistro: ROS kinetic pcl dependency conflict
Hi guys,
There was a new release of libvtk6-dev on 2020-11-30 on ubuntu xenial, that conflicts with the osrf one, and in consequence with ros-kinetic-pcl-ros package.
The osrf release for vtk6 is 6.2.0+dfsg1-10build1+debian11.1+osrf1.
As the most updated" version now, is the ubuntu updates one we are not installing the osrf version.
Can we have an update on this lib?
Related pcl issue
Thanks!
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 9
- Comments: 19 (15 by maintainers)
Commits related to this issue
- Remove workaround for libvtkproj. Recent PCL dependency issue has been resolved in the latest Kinetic release. See: https://github.com/ros/rosdistro/issues/27538 for issue and https://discourse.ros.or... — committed to aws-ros-dev/colcon-bundle by zmichaels11 6 years ago
- Remove workaround for libvtkproj due to fix with new Kinetic release. The new Kinetic release fixes the issue with pcl and vtk, so the workaround of rebuilding from source within the workspace is no l... — committed to aws-ros-dev/colcon-bundle by zmichaels11 6 years ago
- Remove workaround for libvtkproj due to fix with new Kinetic release. The new Kinetic release fixes the issue with pcl and vtk, so the workaround of rebuilding from source within the workspace is no l... — committed to aws-ros-dev/colcon-bundle by zmichaels11 6 years ago
I just talked with @kyrofa and since the upstream libvtk and libpcl are both now consistent the simplest solution is to do the general rebuild of Kinetic to use the consistent libproj. Although it’s not an ABI break, the solution is similar, we will rebuild all packages in Kinetic depending on libvtk6 and anyone with compiled binary distributions will have to do the same. This will take some server time but will provide the simplest solution in the long run.
Process:
rebuild all kinetic packages on top of the new libvtk6
Dependencies of libvtk6-dev
Dependencies of libpcl-dev
Selection listings:
Yeah, to clarify, the state of Ubuntu before the bugfix was:
As a result, anyone using libvtk6 ended up with errors because they were using a library that required libproj to be installed, but it didn’t depend on it (bug 1). Also, anyone using cmake to link to pcl ended up with build errors because they were trying to link to a library that didn’t exist (bug 2). It was just all-around broken.
The fix that Open Robotics got into their Debian archive was to modify libvtk6 to start building and using its vendored libproj again, which made the libpcl in Xenial work because it could find that vtkproj4 library again. However, the vendored libproj is not ABI compatible with the system libproj, so that’s not something I could safely make happen in Xenial. I instead made libvtk6 properly depend upon libproj, and then rebuilt libpcl so it didn’t have a library that didn’t exist in its cmake config.
That’s my thinking anyway, yes. Right now things like
pcl_rosConfig.cmakeandcostmap_2dConfig.cmakecontain vtkproj4. The possible fixes are:No, I think that will break. It’s exactly the opposite situation of the breakage that was in Xenial before this happened:
I suspect that will be one big segfault for anyone trying to use libpcl.
As far as I understand it, it may not quite be the same. I believe you followed the Debian reversion back to the vtk-vendored libproj, right? We can’t do that in Ubuntu as it would have broken ABI, so I tried to fix it by instead pushing all the way through to using the system libproj by adding the dep and rebuilding libpcl to have the proper library in its cmake config files. In a way I kinda broke your ABI by… not breaking ABI 🤔 . And then the pcl rebuild is the cherry on top. More info here. @tfoote we can set up a time to chat tomorrow if you like.