Closed MankaranSingh closed 6 months ago
Are you running
$ source install/setup.bash
in your colcon workspace, like the demo here, before you run your fleet adapter? If the colcon workspace isn't sourced then the linker won't be able to find those libraries.
If that's not the problem then I think it's likely that you don't have a clean build. My best guess is that you have some cmake caches that are linking against compiled RMF message libraries that were in /opt/ros/humble/lib
but which were removed when you uninstalled the RMF binaries.
I recommend running $ rm -rf build install
in your colcon workspace directory and then rerunning the colcon build command.
I totally uninstalled everything and retried with ros2 iron. Still no luck. But it's definitely some issue with my system because otherwise everything looks fine on another system which has fresh ubuntu Installed.
Not sure why it's behaving like that.
Found the issue. I inspected the generated .so files for msgs package and strangely they had python-36m
in their name while my default python version is 3.10. I uninstalled python 3.6 and everything seems to work now.
Before proceeding, is there an existing issue or discussion for this?
Description
I am on ubuntu 22.04 using ros2 humble. Initially I installed binary version of open rmf but saw that easy_fleet is only available in main branch so i decided to build from source. I uninstalled the binaries and building rmf is successful without errors but when launching any demos i get: