ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
From the comments of @gvdhoorn and @marguedas :
Using ROS REP 2001 and python3-rosinstall_generator
, we can generate our own our own ros2.repo to download the source with the following command:
rosinstall_generator ros_core --rosdistro crystal --deps > ros_core.install
vcs-import src < ros_core.install
I obtain the following packages in my /src folder. I still have to check if all the core packages are presents and maybe remove other rmw_implementations (connext/opensplice)
2 | No.2 Revision |
From the comments of @gvdhoorn and @marguedas :
Using ROS REP 2001 and python3-rosinstall_generator
, we can generate our own our own ros2.repo to download the source with the following command:
rosinstall_generator ros_core --rosdistro crystal --deps > ros_core.install
vcs-import src < ros_core.install
I obtain the following packages in my /src folder. I still have to check if all the core packages are presents and maybe remove other rmw_implementations (connext/opensplice)
[EDIT]
Using rosinstall might generate some issues as it generate is install file from ros-gdb repos instead of ros/ros2/eProsima repos ? If using the default branches/tags seems to not lead to a dependency problem, using upstream branch did lead of some missing dependencies while building.
3 | No.3 Revision |
From the comments of @gvdhoorn and @marguedas :
Using ROS REP 2001 and python3-rosinstall_generator
, we can generate our own our own ros2.repo to download the source with the following command:
rosinstall_generator ros_core --rosdistro crystal --deps > ros_core.install
vcs-import src < ros_core.install
I obtain the following packages in my /src folder. I still have to check if all the core packages are presents and maybe remove other rmw_implementations (connext/opensplice)
[EDIT]
Using rosinstall might generate some issues as it generate is install file from ros-gdb repos instead of ros/ros2/eProsima repos ? If using the default branches/tags seems to not lead to a dependency problem, using upstream branch did lead of some missing dependencies while building.
4 | No.4 Revision |
From the comments of @gvdhoorn and @marguedas :
Using ROS REP 2001 and python3-rosinstall_generator
, we can generate our own our own ros2.repo to download the source with the following command:
rosinstall_generator ros_core --rosdistro crystal --deps > ros_core.install
vcs-import src < ros_core.install
I obtain the following packages in my /src folder. I still have to check if all the core packages are presents and maybe remove other rmw_implementations (connext/opensplice)
[EDIT]
Using rosinstall might generate some issues as it generate is its install file from ros-gdb repos instead of ros/ros2/eProsima ros|ros2|eProsima repos ? If using the default branches/tags seems to not lead to a dependency problem, using upstream branch did lead of some missing dependencies while building.