[ros-users] missing generated lisp-messages in debian packages for groovy

Dirk Thomas dthomas at osrfoundation.org
Thu Jun 13 22:03:17 UTC 2013

On 13.06.2013 13:12, Georg Bartels wrote:
> Hi Dirk,
>> The current Debian packages do include generated lisp files for messages.
>> But they are not located in the message folder but under
>> share/common-lisp/ros/*.
> Thanks for the clarification. I was not fully aware of that. However, see below...
>> The problem with the current available packages in the public
>> repository is that they contain invalid code which makes them not
>> loadable.
> ... I just installed the debian package ros-groovy-arm-navigation. It's a stack also containing arm_navigation_msgs which I can find using roscd --msg-defintions and generated cpp-code all there. If I
> now cd to /opt/ros/groovy/share/common-lisp/ros I do not find a sub-dir arm_navigation_msgs. I hope I'm not overlooking something extremely obvious here because then it's a bit embarrasing...

Well, I can confirm that it is the case for arm-navigation (even from shadow-fixed).
Than I guess that is the third issue we are facing since other Debian packages include the lisp files correctly (e.g. std_msgs, actionlib_msgs, turtlesim).
It could be generally the case for dry packages since on a first look I only see lisp files of wet stuff being installed from Debians.

>> The temporary fix to check them out and build them locally works
>> since the issue has been fixed in the source repositories.
> Yup. I can confirm that this current fix is working. :)

But even when building a dry package with messages from source I don't get any lisp files.
So I would suspect that your workaround to build from source does not work for dry stuff.
Can you confirm that?
Above it sounds like a build from source would work for you.
Is that also true for dry stuff?

- Dirk

More information about the ros-users mailing list