[Bug 1573234] Re: unable to link: cannot find libvtkproj4

[Kyle Fazzari]

** Description changed:

  [Impact]
  
   * Any code that links to libraries provided by libpcl1.7 (which depends
  on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)
  
   * This has been fixed in Debian, but in a way that breaks ABI
  
   * See this change through all the way by adding libproj-dev as a
  dependency to libvtk6-dev, and rebuild pcl such that it uses the system
  libproj instead of the vtk-vendored libproj
  
   * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
  missing dependency) and one for pcl (a no-change rebuild using the
  earlier patch for vtk6). As a result, they cannot be uploaded into
  -proposed at the same time. vtk6 must happen first, and pcl only once
  vtk6 has been built.
  
  [Test Case]
  
-  * Build software that uses PCL (e.g. https://github.com/ros-
- perception/perception_pcl) and watch it fail
+  * Install vtk6-dev and libpcl-dev from Xenial
  
-  * Apply this patch, build and install vtk6-dev, then rebuild PCL using
- it. Then watch your previous build failure succeed.
+  * Use them to build this project: https://github.com/kyrofa/pcl-sru-
+ test (borrowed from the bug referenced above) .
+ 
+ * You'll first note that it fails to build because it needs libproj-dev
+ installed. Apply the first patch (to vtk) in this SRU, rebuild and
+ install that version of vtk.
+ 
+ * Build again, and you'll note that it fails to link to vtkproj4. This
+ is libproj that was vendored by vtk, but should not be used at all in
+ Xenial (it's actually building against the system libproj). This is
+ fixed by the second patch (to pcl) in this SRU, a no-change rebuild that
+ causes the cmake config to be regenerated to properly link to the system
+ libproj instead of the vtk-vendored libproj. Rebuild and install that
+ version of pcl.
+ 
+  * Finally, the build should succeed.
  
  [Where problems could occur]
  
   * This patch doesn't change ABI or API, but does add a dependency
  
   * Problems could potentially occur if clients worked around this issue
  by hacking their projects to link to vtkproj, but known users (ROS) have
  vendored Debian's fix into their repos as opposed to working around the
  bug, thus regressions seem unlikely

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1573234

Title:
  unable to link: cannot find libvtkproj4

Status in pcl package in Ubuntu:
  New
Status in vtk6 package in Ubuntu:
  Fix Released
Status in pcl source package in Xenial:
  Confirmed
Status in vtk6 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Any code that links to libraries provided by libpcl1.7 (which
  depends on vtk6) fails to link because it cannot find vtkproj4 (see
  https://github.com/PointCloudLibrary/pcl/issues/1594 for example)

   * This has been fixed in Debian, but in a way that breaks ABI

   * See this change through all the way by adding libproj-dev as a
  dependency to libvtk6-dev, and rebuild pcl such that it uses the
  system libproj instead of the vtk-vendored libproj

   * IMPORTANT: This fix is a two-patch fix, one for vtk6 (adding the
  missing dependency) and one for pcl (a no-change rebuild using the
  earlier patch for vtk6). As a result, they cannot be uploaded into
  -proposed at the same time. vtk6 must happen first, and pcl only once
  vtk6 has been built.

  [Test Case]

   * Install vtk6-dev and libpcl-dev from Xenial

   * Use them to build this project: https://github.com/kyrofa/pcl-sru-
  test (borrowed from the bug referenced above) .

  * You'll first note that it fails to build because it needs libproj-
  dev installed. Apply the first patch (to vtk) in this SRU, rebuild and
  install that version of vtk.

  * Build again, and you'll note that it fails to link to vtkproj4. This
  is libproj that was vendored by vtk, but should not be used at all in
  Xenial (it's actually building against the system libproj). This is
  fixed by the second patch (to pcl) in this SRU, a no-change rebuild
  that causes the cmake config to be regenerated to properly link to the
  system libproj instead of the vtk-vendored libproj. Rebuild and
  install that version of pcl.

   * Finally, the build should succeed.

  [Where problems could occur]

   * This patch doesn't change ABI or API, but does add a dependency

   * Problems could potentially occur if clients worked around this
  issue by hacking their projects to link to vtkproj, but known users
  (ROS) have vendored Debian's fix into their repos as opposed to
  working around the bug, thus regressions seem unlikely

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcl/+bug/1573234/+subscriptions