![]() rosbuild is not recommended or maintained anymore but kept for legacy. These are the two available methods for organizing and building your ROS code. Note: Throughout the tutorials you will see references to rosbuild and catkin. Setup.*sh files are created as a by-product of building or installing catkin packages Rosbuild workspaces provide setup.*sh files using tools like rosws ROS packages installed with package managers provide setup.*sh files. ![]() If they are not then you might need to 'source' some setup.*sh files.Įnvironment setup files are generated for you, but can come from different places: A good way to check is to ensure that environment variables like ROS_ROOT and ROS_PACKAGE_PATH are set: If you are ever having problems finding or using your ROS packages make sure that you have your environment properly setup. This makes developing against different versions of ROS or against different sets of packages easier. This is required because ROS relies on the notion of combining spaces using the shell environment. When working with ROS packages from source or when creating a new ROS package, you should always work in a directory that you have access to, like your home folder.ĭuring the installation of ROS, you will see that you are prompted to source one of several setup.*sh files, or even add this 'sourcing' to your shell startup script. Note: If you installed ROS from a package manager like apt, then those packages will not be write accessible and should not be edited by you the user.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |