[ros-users] Unifying the structure of ROS

Top Page
Attachments:
Message as email
+ (text/plain)
+ (text/html)
Delete this message
Reply to this message
Author: Dominick Vanthienen
Date:  
To: ros-users@code.ros.org
Subject: [ros-users] Unifying the structure of ROS



Dear fellow ROS-users,

I would like to make a package with some functional C class and examples
of components/nodes that use that functionality.
An example can be found on:
http://svn.mech.kuleuven.be/repos/orocos/trunk/kul-ros-pkg/SSC32/
The files in the src/ directory contain the functionality and
orocosSSC32Example/ directory contains an example Orocos component which
uses this functionality.
In this example the second directory is also a package (nested
packages)=> you'll have to add it to your $ROS_PACKAGE_PATH seperatly in
order to get this working.
Alternative could be:
*a seperate package next to the package with the functionality, but this
will lead to a huge number of packages: (one for the C functionallity,
one for a rosnode example, one for an orocos component example...)
*everything in one package: but then people need to install Orocos (RTT,
because it will be in the manifest) for functionality that's not Orocos
specific (then it has no use of making first a C class...)
*...

What solution would be most appropriate?

Thanx for your comments

Nick