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 |
Is it possible to list which boost libraries are depended
For Boost specifically: no, not with any of the tools ROS provides for listing/resolving/installing dependencies. That is not a limitation of those tools, but is due to the fact that there is only a single boost rosdep key (this one), and that maps to libboost-all-dev on Ubuntu. If there were rules for each part of Boost individually, then what you suggest could be supported.
One reason I can think of why that is not done is that it introduces a lot of overhead as all these rules will have to be managed, kept up to date, checked for each ROS release and additional OS that gets supported, etc. It might also not be possible to install separate parts of Boost on some platform+OS combinations.
To see which libraries are really needed, you could use ldd.
If you're concerned about the sizes of packages and want/need more control over dependencies you could consider looking at meta-ros.
| | 2 | No.2 Revision |
Is it possible to list which boost libraries are depended
For Boost specifically: no, not with any of the tools ROS provides for listing/resolving/installing dependencies. That is not a limitation of those tools, but is due to the fact that there is only a single boost rosdep key (this one), and that maps to libboost-all-dev on Ubuntu. If there were rules for each part of Boost individually, then what you suggest could be supported.
One reason I can think of why that is not done is that it introduces a lot of overhead as all these rules will have to be managed, kept up to date, checked for each ROS release and additional OS that gets supported, etc. It might also not be possible to install separate parts of Boost on some platform+OS combinations.
And that is ignoring the fact that developers would also have to figure out which Boost functionality maps to which libraries.
To see which libraries are really needed, you could use ldd.
If you're concerned about the sizes of packages and want/need more control over dependencies you could consider looking at meta-ros.
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.
