You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm really confused by the RPATH behavior with some packages... If I build it with my janky "hermetic" setup, certain things always link to the libs (e.g. rclcpp, rcl, rcutils, std_msgs).
Even attempting to use the Kitware instructions for specifying RPATH in a build, I can't seem to make any difference...
Random editorial: TTBOMK, the ROS packaging philosophy is to strip the RPATHs to permit hot-swapping libs; however, I would still like to make C++ binaries fully specified without needing special environment variables, esp. relevant to usage with Bazel (relates ).
the ROS packaging philosophy is to strip the RPATHs to permit hot-swapping libs
That is not really a "ROS packaging philosophy" but standard CMake behavior.
I can't recommend anything more than "whatever CMake offers to customize the RPATH behavior". Maybe asking on answers.ros.org will yield more useful feedback to your questions since more people read it. If you do so please reference the question here for future readers to find it.
Also since the ticket isn't really an actionable items for this repo I will go ahead and close it. Please feel free to continue commenting.
May I ask if it's possible to force CMake to link with RPATHs?
Here's my current attempt:
https://github.com/EricCousineau-TRI/repro/blob/50b26e2/ros/ros2_bazel_prototype/NOTES.md
Some commentary:
rclcpp
,rcl
,rcutils
,std_msgs
).Random editorial: TTBOMK, the ROS packaging philosophy is to strip the RPATHs to permit hot-swapping libs; however, I would still like to make C++ binaries fully specified without needing special environment variables, esp. relevant to usage with Bazel (relates ).
May tangentially relate ros2/ros2#457
BTW Please let me know if I'm using "RPATH" terminology incorrectly... I more-or-less just pattern match when I see this word + shell commands.
UPDATE: Posted an update in colcon/colcon-bazel#14 about using Bazel to resolve the paths, and some
rmw
stuff.The text was updated successfully, but these errors were encountered: