ros-tooling/setup-ros

Compilation failure because of pluginlib in ros-tooling/setup-ros@0.0.25

Closed this issue · 4 comments

Description

Expected Behavior

Compilation failure should not occur from the base libraries (pluginlib in this case) installed in the setting.

Actual Behavior

Compilation crash with the following error code.

--- stderr: plugin_example
In file included from /root/target_ws/src/ros2_tutorial/plugin_example/src/plugin_loader.cpp:21:
/opt/ros/foxy/include/pluginlib/class_loader.hpp:55:10: fatal error: boost/shared_ptr.hpp: No such file or directory
55 | #include <boost/shared_ptr.hpp>
| ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

To Reproduce

** Steps to reproduce the behavior, e.g.

  1. Use the below and test CI
    • uses: ros-tooling/setup-ros@0.0.25
    • uses: ros-tooling/action-ros-ci@0.0.19
  2. Logs print error
    --- stderr: plugin_example
    In file included from /root/target_ws/src/ros2_tutorial/plugin_example/src/plugin_loader.cpp:21:
    /opt/ros/foxy/include/pluginlib/class_loader.hpp:55:10: fatal error: boost/shared_ptr.hpp: No such file or directory
    55 | #include <boost/shared_ptr.hpp>
    | ^~~~~~~~~~~~~~~~~~~~~~
    compilation terminated.

System (please complete the following information)

  • OS: ubuntu-20.04
  • ROS 2 Distro: foxy

Thanks for the report - is there a public repository that you are running this on? That would help us reproduce this issue.

@emersonknapp

Thank you for your reply.

Error message from CI: https://github.com/JaehyunShim/ros2_tutorial/runs/1143028540?check_suite_focus=true#step:3:333
Source code: https://github.com/JaehyunShim/ros2_tutorial/tree/master/plugin_example

Uncomment the line 36-46, 51-63 in the CMakeLists.txt file and run CI, then you will see the same error code. I didn't see it when I compiled the package on my local PC though.

Thank you in advance,
Jaehyun

@JaehyunShim I'm going to close this as there have been significant new releases of both action-ros-ci and setup-ros (0.1.0). Please let me know if you are still seeing this problem and we can reopen the issue.

There's an open PR fixing this in the pluginlib repo.