Hey I am out for this weekend , I'll look into it in detail and publish a fix asap
- Sent from my Android Mobile Device. Pardon the brevity.
Hey guys,
Do you have an explanation for this behaviour, ie why do the packages in the host filesystem have to be complied as well?
As long as the rce-ros client is used the ROS message definition aren't even loaded in the RobotEndpoint (they are only loaded in the in case a Converter interface is used...), which could explain why the messages definition has to be available in the host machine. Furthermore, the message definitions are required to launch the rce-ros client, but then you would get an error there and not in the in the container.
I assume that the faulty povisioning has somehow screwed up the system (I guess it's still the system where ROS had to be installed manually, after this strange error with /opt/ros/fuerte/setup.sh not found during the provisioning...).
What do you think?
Dominique