forked from robotology/yarp
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathyarp_with_ros_configure.dox
28 lines (23 loc) · 1.26 KB
/
yarp_with_ros_configure.dox
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
/*
* Copyright (C) 2011 and 2016 Istituto Italiano di Tecnologia, iCub Facility.
* CopyPolicy: Released under the terms of the LGPLv2.1 or later, see LGPL.TXT
*
*/
/**
* @page yarp_with_ros_configure Configure YARP to use ROS
Not all versions of YARP have ROS support enabled by default. In this case
you'll need to turn the following flags on in CMake before (re-)compiling YARP:
\li CREATE_OPTIONAL_CARRIERS (for support of ROS wire protocols)
\li ENABLE_yarpcar_tcpros_carrier (the usual protocol for topics)
\li ENABLE_yarpcar_rossrv_carrier (tcpros with minor tweaks for services)
\li ENABLE_yarpcar_xmlrpc_carrier (used by ros nameserver and node interfaces)
If you have an older version of YARP, you may need to rely on yarpidl_rosmsg
program, as per the tutorial. In that case turn on these flags (which are no longer
required in newer versions of YARP):
\li CREATE_IDLS (for support of ROS .msg/.srv files). Reconfigure after setting this flag.
\li ENABLE_yarpidl_rosmsg (a program to convert .msg/.srv files into YARP-usable form)
YARP does not link to any parts of the ROS codebase, so don't
worry about how to tell YARP where to find the ROS libraries,
it doesn't need them. You do not need to have ROS installed
in order to interoperate with it across the network.
*/