ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2022-02-04 02:33:18 -0500 | received badge | ● Student (source) |
2020-11-11 08:11:13 -0500 | received badge | ● Famous Question (source) |
2020-09-02 09:52:54 -0500 | received badge | ● Notable Question (source) |
2020-07-31 17:48:47 -0500 | commented answer | Colcon build include path from overlay workspace Thank you! |
2020-07-31 17:47:41 -0500 | marked best answer | Colcon build include path from overlay workspace How can I control which include paths will be used when colcon builds a package? I would like to use the includes form a package in my current workspace instead of the ones of the same package in the ros2 underlay workspace. It seems to look in both places, but unfortunately the underlay workspace has priority. As a concrete example, I'm trying to build the master branch of rosbag2. I am using the latest foxy (patch1) binary release. The build currently fails because it is trying to use the rosbag2_cpp include files from the foxy release when building the rosbag_transport package. Instead it should be looking for the rosbag2_cpp includes in the current workspace. (the max_bagfile_size has been added in rosbag2_cpp/storage_options.hpp on master (current workspace) but it is not present in the foxy release, see error below) I solved the build errors by simply deleting the rosbag2 library out of the ros2 binary installation so that the includes from the current workspace are used. However I am thinking there must be a better way to do this. Sourcing ros2 environment, then creating a workspace and cloning rosbag2 into it, running colcon build: Edit: These are the compiler calls without --merge-install: and with --merge-install: |
2020-07-31 17:47:41 -0500 | received badge | ● Scholar (source) |
2020-07-31 17:39:08 -0500 | received badge | ● Popular Question (source) |
2020-07-31 13:16:36 -0500 | commented question | Colcon build include path from overlay workspace I posted the compiler calls, I don't see how the include sequence is generated from the CMakeLists.txt. I'm not familiar |
2020-07-31 13:13:33 -0500 | edited question | Colcon build include path from overlay workspace Colcon build include path from overlay workspace How can I control which include paths will be used when colcon builds a |
2020-07-31 13:08:36 -0500 | commented question | Colcon build include path from overlay workspace I can confirm that with --merge-install it compiles fine for me too. |
2020-07-29 18:21:00 -0500 | asked a question | Colcon build include path from overlay workspace Colcon build include path from overlay workspace How can I control which include paths will be used when colcon builds a |