-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathmanifest
85 lines (80 loc) · 2.67 KB
/
manifest
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
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
#
# Informations about the manifest of autoproj can be found here:
# http://www.rock-robotics.org/documentation/autoproj/customization.html
#
package_sets:
- github: rock-core/package_set
- gitorious: rock-tutorials/package_set
- github: rock-simulation/package_set
# Uncomment to enable the Rock/ROS bridge
# You will also have to uncomment some lines in the layout below
# - gitorious: rock-ros/package_set
# Layout. Note that the rock.base, rock.toolchain and orocos.toolchain sets are
# imported by other rock sets.
layout:
- rock.core
- rock
- rock.tutorials
- rock.simulation
# Uncomment to enable the Rock/ROS bridge
# You will also have to uncomment some lines in the package_sets above
# - rock.ros
# Uncomment to checkout and build all tutorials
# - rock.tutorials
# The layout section specifies what to build, and where to build it (as a
# subdirectory of the root installation directory). In the example below, all
# the packages of the rock.toolchain package set will be built, in the tools/
# subdirectory: source in tools/typelib, tools/orocos/rtt, ... and installed
# files in build/tools/typelib, build/tools/orocos/rtt, ...
#
# layout:
# - tools:
# - rock.toolchain
#
# Single packages can also be selected instead of whole package sets. The
# package names are interpreted as a regular expression, so it is possible to
# do:
#
# layout:
# - tools:
# - typelib
# - utilmm
# - orocos/
#
# The first two match the typelib and utilmm packages, while the second one
# match all packages in which "orocos/" is found.
#
# Again, note that if a layout section is present, only the packages listed
# there will be built.
# Package exclusion: packages can be completely excluded from the build. This is
# an alternative way than using the layout, mainly useful if you want to enable
# all packages but a few ones. As with layout, the names are actually regular
# expressions.
#
exclude_packages:
# needs special driver
- drivers/camera_ids
# lost source
- drivers/imar
- drivers/orogen/imar
- drivers/stim300
- drivers/orogen/stim300
# broken osdeps 12.04, broken in testing
- slam/ceres_solver
# broken
- drivers/camera_aravis
- drivers/orogen/camera_aravis
- drivers/orogen/kinect
# others
- external/snap
- image_processing/orogen/video_streamer
# Ignoring packages: same principle than package exclusion, but this time the
# packages are considered to be installed and up-to-date. This is useful if you
# want to use an already installed software package.
#
# For instance, let's assume the orocos/rtt is already installed on your
# machine. You would then simply do:
#
# ignored_packages:
# - rtt
#