ruffsl
May 30, 2020, 9:48pm
15
Martin_Guenther:
I only use the Dockerfile I posted in the CI for rospy_message_converter and others, and its only purpose is to check that all dependencies are properly listed in the package.xml, build the package, and run the tests.
We are discussing the idea of adding something like osrf/ros:<distro>-devel
, that would sort of mimic what we’ve been doing with osrf/ros2:devel
, but be distro specific, where the common build tools, repos and dev environment are preconfigured, but with no ros distro packages installed:
opened 03:19PM - 28 May 20 UTC
It's not uncommon to see people writing their own image from scratch because the… ROS images bring in too many dependencies.
While the ROS docker images are thought of as "for deployment" there is a strong use case for CI systems or environments for building packages.
Similarly to how we provide a osrf/ros2:devel image for ROS 2, we could consider providing a set of devel images for ROS 1.
These images would :
- be distro specific: osrf/ros:devel-kinetic osrf/ros:devel-noetic-buster
- have the ROS apt repo setup
- install the released version of catkin for the corresponding distro
- install the dependencies listed at https://wiki.ros.org/melodic/Installation/Ubuntu#Installation.2FUbuntu.2FBinariesBuildDependencies.Dependencies_for_building_packages
- have rosdep initialized and installed
- have catkin_tools installed ?