Ask Your Question
3

[Groovy Beta 1] Having trouble installing console_bridge required by vision_opencv

asked 2012-12-11 03:34:02 -0500

Kevin gravatar image

I have installed groovy beta following these instructions on OSX and all of the core ROS stuff is working.

I am having a difficult time getting the higher level packages I need built (vision_opencv and navigation). I get stuck on console_bridge (https://github.com/ros/console_bridge) which is required for class_loader and pluginlib.

Console_bridge doesn't seem to be a package … not sure what to do with it. Should I try to make a homebrew formula for it and install it as a system dependency? If yes, then I will need to figure out how to write a cmake or package config file for it ... haven't done that before.

edit retag flag offensive close merge delete

2 Answers

Sort by » oldest newest most voted
2

answered 2012-12-11 05:48:00 -0500

WilliamWoodall gravatar image

I am actively working on the general source install instructions:

http://ros.org/wiki/groovy/Installation/Source/New

Currently they are targeted at Ubuntu and have some problems still, but the important thing is that this page tells you how you can use wstool to get all of the packages for a given variant (like desktop or desktop-full) and how you can use the latest rosdep to fetch all dependencies (even on OS X Homebrew). I'll summarize those here:

$ mkdir ~/groovy_catkin
$ cd ~/groovy_catkin
$ wstool init src http://packages.ros.org/web/rosinstall/generate/raw/groovy/desktop
$ rosdep install --from-paths src --ignore-src --rosdistro groovy -y
$ ./src/catkin/bin/catkin_make
$ ./src/catkin/bin/catkin_make install

That should have fetched, resolved, built, and installed all of the wet (catkin) packages that make up the desktop variant into the ~/groovy_catkin/install folder. You can then source the setup.bash in that folder to source your newly built groovy space.

I have built and installed the desktop variant on OS X using Homebrew last week. But there potentially remain some snags which have been fixed but not released yet. I am currently working my way through the desktop-full variant fixing things as I go (on Ubuntu and OS X).

The thing still lacking from the instructions I linked is the part where you download and build/use the dry (rosbuild) parts of the variant. I hope to have that part soon (it is not hard, I just haven't finished testing the wet stuff yet).

edit flag offensive delete link more

Comments

1

Thanks William. Great to see progress here. I see that the rosinstall files you use reference tarballs for specific versions. How are updates then supposed to work? I guess wstool update wouldn't do the job.

Lorenz gravatar image Lorenz  ( 2012-12-11 21:01:33 -0500 )edit
1

That is something we have not addressed yet, but we will have a "devel" version of that url which will checkout everything instead, which could be updated. We didn't do that initially because it was much faster to fetch the tarballs.

WilliamWoodall gravatar image WilliamWoodall  ( 2012-12-11 21:04:22 -0500 )edit
0

answered 2012-12-11 04:10:00 -0500

Lorenz gravatar image

When installing ros packages from source, I do not suggest to use the development repos but the actual release repos as referenced in groovy.yaml unless you are doing real development in the package. The release repos are used to generate the debian packages. One reason for using them instead of the dev repos is that some packages are patched to add a catkin CMakeLists and package.xml file. One example is console_bridge which is actually a ros independent library and only converted to a catkin library for the release. To use a release repo, you need to check out the branch release/<package_name> and build that.

edit flag offensive delete link more

Comments

This is a good point. Just for everyones information, console_bridge will have the package.xml and everything you need to build it in the upstream source starting with Hydro.

William gravatar image William  ( 2013-03-26 07:09:10 -0500 )edit

I'm not able to resolve the console_bridge rosdep key in Indigo. Should my package build-depend on rosconsole_bridge instead?

mikepurvis gravatar image mikepurvis  ( 2015-01-20 11:21:06 -0500 )edit

@mikepurvis I think it is libconsole-bridge-dev now (since it has moved upstream into Debian).

William gravatar image William  ( 2015-01-20 13:49:50 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2012-12-11 03:34:02 -0500

Seen: 631 times

Last updated: Dec 11 '12