ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

Difference between Jenkins log and generated package (lib prefix)

asked 2019-11-13 05:06:03 -0600

wxm gravatar image

Hi, I am trying to debug a failure in setting up the CMake variables for library installation.

  1. I am inspecting the generated package (ros-kinetic-eigenpy, version 1.6.5-1) by installing in a new Kinetic docker. The pkg-config eigenpy.pc is installed in /opt/ros/kinetic/lib/x86_64-linux-gnu/pkgconfig, while the library itself is in /opt/ros/kinetic/lib. This would suggest an issue setting up the CMAKE_INSTALL_LIBDIR.
  2. After reviewing the output of the latest Jenkins job, it appears there it correctly installs without the x86_64-linux-gnu prefix (in devel_isolated).

Am I missing something obvious here why on Jenkins it appears to install correctly but the packaged version on ros-testing has it using the prefix?

I appreciate any insights

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2019-11-13 15:21:38 -0600

nuclearsandwich gravatar image

The job output you're linking is for a devel job which tests the latest version of packages in a source repository. The job which builds the Kinetic eigenpy debian package is http://build.ros.org/job/Kbin_uX64__e...

You can also run a local copy of the binarydeb job using the ros_buildfarm library: https://github.com/ros-infrastructure...

edit flag offensive delete link more

Comments

Thank you - this is what I was looking for.

It turns out the original problem is related to an old version of debhelper on kinetic. Versions >10.2.1 solve the problem. I will work on a workaround.

wxm gravatar image wxm  ( 2019-11-14 07:31:01 -0600 )edit

@nuclearsandwich: I have described the issue I am trying to debug with references in https://github.com/stack-of-tasks/eig.... It boils down to the use of GNUInstallDirs using old versions of debhelper on 16.04 appending the architecture to lib. As such the pkgconfig files end up in lib/arch/pkgconfig while the library ends up in lib/. Is there a recommended workaround? (This is a REP136 released third-party package)

wxm gravatar image wxm  ( 2019-11-14 09:19:01 -0600 )edit

Question Tools

2 followers

Stats

Asked: 2019-11-13 05:06:03 -0600

Seen: 170 times

Last updated: Nov 13 '19