The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
I recommend reading up about the rosinstall generator. There are instructions for how to do a source installation using it like the standard source install instructions
As much as it's great to keep things isolated the cost of compiling everything from source is very high for individual developers. There are a lot of packages int he ROS ecosystem and the aggregate compile time ends up being many hours versus minutes. And I know of developers who will wait a few days for binaries to be released instead of pulling external packages from source.
So I'd definitely suggest that you look hard at docker or at least chroots to allow you to reuse the binary packages unless you're planning a single installation and deployment and not to be actively developing.
Note that there are official ROS docker images as well as several higher level images from OSRF
| | 2 | No.2 Revision |
I recommend reading up about the rosinstall generator. There are instructions for how to do a source installation using it like the standard source install instructions
There are options to exclude specific packages and exclude via path for things already installed.
As much as it's great to keep things isolated the cost of compiling everything from source is very high for individual developers. There are a lot of packages int he ROS ecosystem and the aggregate compile time ends up being many hours versus minutes. And I know of developers who will wait a few days for binaries to be released instead of pulling external packages from source.
So I'd definitely suggest that you look hard at docker or at least chroots to allow you to reuse the binary packages unless you're planning a single installation and deployment and not to be actively developing.
Note that there are official ROS docker images as well as several higher level images from OSRF
| | 3 | No.3 Revision |
I recommend reading up about the rosinstall generator. There are instructions for how to do a source installation using it like the standard source install instructions
There are options to exclude specific packages and exclude via path for things already installed.
Your users should source create their own workspace, source the underlay setup file, and then they can use rosinstall generator with the --exclude RPP to skip anything in the underlay to generate their desired set of packages.
As much as it's great to keep things isolated the cost of compiling everything from source is very high for individual developers. There are a lot of packages int he ROS ecosystem and the aggregate compile time ends up being many hours versus minutes. And I know of developers who will wait a few days for binaries to be released instead of pulling external packages from source.
So I'd definitely suggest that you look hard at docker or at least chroots to allow you to reuse the binary packages unless you're planning a single installation and deployment and not to be actively developing.
Note that there are official ROS docker images as well as several higher level images from OSRF
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
