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 |
Ok, so I have worked my way around this issue, and although I have come to an interim conclusion about this (more below) I do not think that I have a definitive answer to my question that puts the problem into perspective...
It seems to me that "rosdep install" (or the "--rosdep-install" option for rosmake) should not be relied upon if your system is ``experimental'' - e.g. Debian or Ubuntu armel.
You may be lucky and the scripts may resolve dependencies into the correct packages for your system, where they exist.
But if you get a dependency error from rosdep and you're on an "experimental" system, abandon "--rosdep-install", build the libraries/packages you need from source or install from backports, and try building your ROS package again using rosmake, leaving out the rosdep step/option. Ignore warnings (for the moment, at least), and if your package installs without errors, you should be set. If you get errors about dependencies that you are sure you built and/or installed, then I have one more silverish bullet, which is to ensure the ".pc" file for your library/package is in the pkg-config path with .pc files (in my case, "/usr/local/lib/pgkconfig/").
Sometimes the ROS package might be looking for a particular .pc filename, like "opencv-2.3.pc", when your build of opencv 2.3 only placed a "opencv.pc" file there. Then, my solution is to create a symbolic link, in this case from "opencv.pc" to "opencv-2.3.pc" in the relevant pkgconfig path.
Hope this helps someone!
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.
