-
Notifications
You must be signed in to change notification settings - Fork 0
/
manifest
54 lines (47 loc) · 1.47 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
# List of VCS information or subdirectories of autoproj/ in which to find
# package set definitions.
package_sets:
- github: rock-core/package_set
- github: rock-core/rock-package_set
- rock.build-tests
layout:
- base/cmake
- base/templates/cmake_lib
- base/scripts
- rock.build-tests
- orogen
- tools/orocos.rb
- gui/orogen/qt_base
exclude_packages:
- gui/vizkit3d
- qwt5
- gui/vizkit
# Examples from the Rock package set
# - github: rock-core/package_set
# The layout section specifies what to build. Can include both whole package sets or single packages.
#
# layout:
# - rock.core
#
# Package exclusion: packages can be completely excluded from the build. This is
# an alternative way than using the layout.
#
# Useful if you want to enable a whole package set except a few packages, or if
# you want to exclude some package's optional dependencies.
#
# exclude_packages:
# - gui/.*
# Ignoring packages: assume that some packages are present on disk. Unlike
# exclude_packages, autoproj will not generate an error if a non-excluded
# package depends on an ignored one, but it will not include the package and its
# dependencies in the build.
#
# For instance, if one assumes that the 'rtt' package is already available on
# the machine *and* you're confident that picking it outside of the workspace
# won't create problems, then simply do:
#
# Note that using this obviously hinders repeatability of the build
#
# ignored_packages:
# - rtt
#