-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ROS Kinetic regression (lib install includes architecture) #116
Comments
There have been some other projects that hit this bug in the past too: ros/console_bridge#15 With a follow up here: ros/console_bridge#19 and ros/console_bridge#29 |
The pkg-config template uses the _FULL_ variables while the install happens without the prefix. This addresses stack-of-tasks#116
Thank you @tfoote. I think I found the issue. The cmake-modules that this project depends on sets variables for where to find the library in the pkg-config template that do not match the ones where it actually gets installed to. I will push for a merge + release to the buildfarm today, this should fix the Pinocchio regression. |
Thank you. Release made:
|
While #120 fixed the mismatch between the pkg-config and the actual installed layout, it didn't resolve the original issue. The toolchain appears to configure in such a way that on Xenial that the system architecture is used in the path ( |
This issue is to track the issues with the
eigenpy
package distributed via the ROS buildfarm on Ubuntu 16.04 which affectspinocchio
(regression, does not build) andmoveit
(works because addedeigenpyConfig.cmake
). Currently, onlypinocchio
and other pkg-config consumers are broken.Note: This problem only happens on 16.04/kinetic due to the old version of
debhelper
.GNUInstallDirs
. On theros_buildfarm
, theCMAKE_INSTALL_FULL_LIBDIR
includes the system architecture for thepkg-config
file, while the library is correctly installed inlib/
.libdir
andpkglibdir
both include the system architecture:Related issues:
@tfoote: Is there any way of resolving this apart from changing the
rules
in the packaging manually (e.g. mrpt-ros-pkg-release/mrpt1-release@17361d7)? The most relevant answer to the issue here is from ros-infrastructure/ros_buildfarm#543 (comment)The text was updated successfully, but these errors were encountered: