There is an ABI conflict between the octomap versions provided by Ubuntu and by the rosdistro package.
liboctomap-dev is currently at 1.9.7 on Ubuntu jammy and noble and the ros-[jazzy/rolling]-octomap version is at 1.10, ros-humble-octomap is at 1.9.8. Linking both version obviously results in undefined behavior and segfaults.
Until this conflict is resolved, we are enforcing the system version liboctomap-dev by depending on libfcl-dev (only rosdep target that depends on liboctomap-dev, currently), and by specifying the version in the CMakeLists.txt of all packages in the build chain. A proper fix would require one of the following options:
getting liboctomap-dev synced with ros-*-octomap or vice versa
adding a liboctomap-dev rosdep target and keeping the version filters
switching to fcl-hpp which provides a proper ros package and only depends on the ros package of octomap
There is an ABI conflict between the octomap versions provided by Ubuntu and by the rosdistro package. liboctomap-dev is currently at 1.9.7 on Ubuntu jammy and noble and the ros-[jazzy/rolling]-octomap version is at 1.10, ros-humble-octomap is at 1.9.8. Linking both version obviously results in undefined behavior and segfaults.
Until this conflict is resolved, we are enforcing the system version liboctomap-dev by depending on libfcl-dev (only rosdep target that depends on liboctomap-dev, currently), and by specifying the version in the CMakeLists.txt of all packages in the build chain. A proper fix would require one of the following options: