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 |
Please see #q252478 for an example workflow when building packages from source.
In general though: try not to build packages in your workspace. Always first try to see whether a package has been released and could be installed using apt. The buildfarm has already done all the dependency resolution for you, keeps you automatically up-to-date and (especially with large packages) it's much more efficient to build something once and re-use the binaries than to have each user compile everything themselves again.
| | 2 | No.2 Revision |
Please see #q252478 for an example workflow when building packages from source.
In general though: try not to build packages in your workspace. Always first try to see whether a package has been released and could be installed using apt. The buildfarm has already done all the dependency resolution for you, keeps you automatically up-to-date and (especially with large packages) it's much more efficient to build something once and re-use the binaries than to have each user compile everything themselves again.
when I down load a package (even s simple toturail package), usually is not native developed for this HW platform.. then when build it usually will report fail by message that short of some other package--then I search it and git clone it from wiki then build--another depedence error jump out... and after 5 round I feel quite boring and anoying.
Not building from source also allows you to avoid this "boring and annoying" part.
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.
