You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After following the Build Dave Environment page in the wiki Installation instructions (native, non-Docker install), my build had unmet dependencies. Specifically, when running roslaunch dave_demo_launch dave_demo.launch, the gripper_controller node died because of an unmet dependency for kdl_parser_py.
Workaround
Running the automagical dependency-installation command rosdep install --from-paths src --ignore-src -r -y resolved this issue because the kdl_parser_py dependency had been declared in a package.xml file.
Proposed Fix
Is it alright if I add the above rosdep command to the installation wiki entry? I'm fairly new to ROS so I'm not sure if another method is preferred, or if the command is omitted for another reason.
I think the real fix is that we should include that package on the sudo apt install command on the Install Directly on Host page. I see in our dockwater Docker image, we install the package ros-${DIST}-kdl-parser-py in this line, added as a new dependency for the uuv_manipulators package. But it hasn't been added to the said installation page.
I've gone ahead and made that fix. While doing that, I compared the list of packages in the instruction page against the apt install list in the dockwater Noetic Dockerfile. ros-${DIST}-urdfdom-py was also missing and now added to the installation page.
The rosdep line suggested in the original post seems reasonable to add as a troubleshoot tip, in case we forget another package like this in the future. That's the recommended command from the rosdep documentation. I don't know where's the best place to add it. It can either be added to the Clone Dave Repositories page as a redundant measure to make sure nothing falls through the cracks, or be added to the Build Dave Environment page as a Troubleshoot section after catkin_make. There should probably be some verbiage as to, if you need to run this command, then we're missing some packages in the sudo apt install line provided, open a ticket to report it.
What do other maintainers think? (@bsb808, preference question)
Observed Behavior
After following the Build Dave Environment page in the wiki Installation instructions (native, non-Docker install), my build had unmet dependencies. Specifically, when running
roslaunch dave_demo_launch dave_demo.launch
, thegripper_controller
node died because of an unmet dependency forkdl_parser_py
.Workaround
Running the automagical dependency-installation command
rosdep install --from-paths src --ignore-src -r -y
resolved this issue because thekdl_parser_py
dependency had been declared in apackage.xml
file.Proposed Fix
Is it alright if I add the above
rosdep
command to the installation wiki entry? I'm fairly new to ROS so I'm not sure if another method is preferred, or if the command is omitted for another reason.Terminal output
The text was updated successfully, but these errors were encountered: