I could be wrong, but I think all of the tools still need to get touched for groovy's catkin.  So anything generated by rosws and rosinstall probably are no good for groovy at the moment, that includes setup.* files and the CMakeLists.txt file generated by rosinstall.

--

On Tue, Oct 2, 2012 at 2:43 PM, Jack O'Quin <jack.oquin@gmail.com> wrote:
I managed to install groovy Debian packages on Oneiric.

But, I am having trouble getting rosws to work with it. When I ran this:

 $ rosws init ~/ros/groovy /opt/ros/groovy/.rosinstall

It only defined this line:

 - setup-file: {local-name: /opt/ros/groovy/setup.sh}

I added these to the generated .rosinstall by hand (by analogy with fuerte):

 - other: {local-name: /opt/ros/groovy/share/ros}
 - other: {local-name: /opt/ros/groovy/share}
 - other: {local-name: /opt/ros/groovy/stacks}

Even then, the generated setup.bash does not seem to source the
installed /opt/ros/groovy/setup.bash. I have to do that by hand in
each new shell.

Before I spend more time chasing this, I wonder: has anyone succeeded
using rosws with groovy already?
--
 joq
_______________________________________________
Ros-release mailing list
Ros-release@code.ros.org
https://code.ros.org/mailman/listinfo/ros-release



--
William Woodall
Willow Garage - Software Engineer
wwoodall@willowgarage.com