Open JackDeSomeTrades opened 3 weeks ago
Many thanks for reporting this! Can you please share code for a minimum working/failing example?
Hi, thanks for responding. I'm not sure if I can provide a minimum failing example.. Perhaps you can try to build and run derived_object_msgs
from here - https://github.com/astuff/astuff_sensor_msgs/tree/master/derived_object_msgs
It requires geometry_msgs
to build and run. It builds well, but using it in any package throws up an error because the package cannot find libgeometry_msgs__rosidl_generator_py.so
The context here is that I'm trying to use the Carla simulator with the ROS_Bridge. The reason I manually built derived_object_msgs
is because ros-humble-derived-object-msgs
isn't available on Robostack for Linux-x86-64 (it was going to be my next pull request).
It could be a good test to see if using the prebuilt package would work better? However, that still doesn't address the core lib
issue.
You do not have the compilers package etc installed - please check our install guide and try again, this could be the culprit.
Tried with installing the compilers, colcon-common-extensions packages etc and still the same behaviour.
If you could please report the steps that need to be taken to reproduce the error, that'd be great. E.g. something like
mkdir -p ~/ws/src
cd ~/ws/src
git clone ...
colcon build ...
ros2 run ...
Solution to issue cannot be found in the documentation.
Issue
I see strange behaviour in populating the
LD_LIBRARY_PATH
environment variable with a native ROS2 Humble install and one installed with RoboStack.Below is an explanatory image with expected behaviour on the left and current behaviour on the right:
This issue is affecting the discovery of
libgeometry_msgs__rosidl_generator_py.so
which is required when generating custom msgs for a package and can be found in../miniforge3/envs/<env-name>/lib/
.In a native install, sourcing the
setup.ba/z/sh
file populates this path in theLD_LIBRARY_PATH
while sourcing the same setup file in../miniforge3/envs/<env-name>/setup.ba/z/sh
does not.Exporting the path manually in every terminal seems to solve the discovery issue but this is not expected nor preferred behaviour.
I can't seem to find what's causing this bug but I hope you may be able to help.
Installed packages
Environment info