-
Notifications
You must be signed in to change notification settings - Fork 421
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
Document how to work with the dual release to Noetic #533
Comments
I am not sure if this is the best place (i.e. the place where you can find the most interest people in this). The issue of two different versions of fcl being released in apt Debian/Ubuntu repo and in ROS build farm seems to be more a problem of ROS distribution rather then an upstream problem of fcl (that can be consume in several ways, Debian binaries, ROS Debian binaries, as bazel external, via vcpkg, via conda-forge, etc etc). Some related issue on rosdistro seem to be ros/rosdistro#26706 and ros/rosdistro#26527, perhaps it could make sense to drop a comment in ros/rosdistro#26527 ? |
Thanks for the redirect, I did not know exactly where to report this. So I'm closing this issue here and discussion will (hopefully) follow in ros/rosdistro#26706 . |
Related issues, but on ROS2: |
Hi, Noticed that by default moveit packages are dependant of |
On Ubuntu Focal with ROS Noetic, there are two installs of libfcl. One system from
libfcl-dev
, and one ROS fromros-noetic-fcl
.I think this needs/deserves a note in Migration guide of ROS Noetic, doesn't it? Is there a way for packages to choose which version they want, which is reliable both during build time and run time?
Build failures like the following are surprising and hard to debug: https://build.ros.org/job/Ndev__robot_body_filter__ubuntu_focal_amd64/1/console
For example, I was unable to recreate this situation on my computer. It seems that CMake chose FCL 0.6.1 (from the logs), then built the library using 0.5 headers (probably because I include only a header that's in 0.5), and the ran the linker with the 0.6.1 library.
It took me about an hour until I figured out what happened. Documenting this and giving some suggestions could save some other people time upgrading their packages to Noetic.
The text was updated successfully, but these errors were encountered: