New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to find dependencies for libconsole-bridge-dev #31

kkspeed opened this Issue Mar 18, 2015 · 2 comments


None yet
3 participants
Copy link

kkspeed commented Mar 18, 2015

I'm trying to use tf with my current project. I added to the manifest.xml, then I run roshask dep. I receive the following message:

Looking for ["libconsole-bridge-dev"], dependencies of /home/bruce/catkin_ws/src/lab1
roshask: Couldn't find path to package (2) libconsole-bridge-dev

It seems that roshask cannot find the package "libconsole-bridge-dev", but this package clearly is installed.

I wonder if I'm doing something wrong or is there any workaround to this?


This comment has been minimized.

Copy link

rgleichman commented Mar 18, 2015

It seems that "libconsole-bridge-dev" is not a ROS Package. Thus it would not be on the ROS_PACKAGE_PATH, so roshask would not be able to find it. Try adding "libconsole-bridge-dev" to the list of ignoredPackages in roshask/src/Ros/Internal/DepFinder.hs:

ignoredPackages = ["genmsg_cpp", "rospack", "rosconsole", "rosbagmigration", 
                   "roscpp", "rospy", "roslisp", "roslib", "boost", "libconsole-bridge-dev"]

This comment has been minimized.

Copy link

acowley commented Mar 18, 2015

Hrmph, is it worth trying to find a good way of differentiating these kinds of dependencies? This mechanism works, but doesn't scale very well. On the other hand, it doesn't seem to cause too much trouble, so maybe a hand-maintained list like this is most expedient. We could add some kind of whitelist that could be pulled out of a file (eg, roshask.ignore) so folks don't have to edit the code.

@acowley acowley closed this in ea34f98 May 1, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment