forked from GNOME/jhbuild
-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathREADME
160 lines (114 loc) · 5.07 KB
/
README
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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
JHBuild README
================================
JHBuild is a tool designed to ease building collections of source
packages, called “modules”.
JHBuild was originally written for building GNOME, but has since been
extended to be usable with other projects.
JHBuild requires Python >= 2.3
Installing JHBuild
-----------
Refer to the 'Getting Started' section of the JHBuild manual:
yelp /jhbuild-source-dir/doc/C/index.docbook
Or refer to the on-line JHBuild manual at:
http://library.gnome.org/devel/jhbuild/stable/getting-started.html.en
Using JHBuild
-------------
JHBuild uses a command line syntax similar to tools like CVS:
jhbuild [global-options] command [command-arguments]
The global JHBuild options are:
-f, --file config
Use an alternative configuration file instead of the default
~/.config/jhbuildrc.
-m, --moduleset moduleset
Use a module set other than the module set listed in the
configuration file. This option can be a relative path if the module
set is located in the JHBuild moduleset folder, or an absolute path
if located elsewhere.
--no-interact
Do not prompt the user for any input. This option is useful if
leaving a build unattended, in order to ensure the build is not
interrupted.
Refer to the JHBuild manual for a complete list of JHBuild commands
and options. The common ones are:
jhbuild bootstrap
The bootstrap command installs a set of build utilities. The build
utilities include autoconf , automake and similar utilities. The
recommended method to install the build utilities is via your
distribution's package management system. The bootstrap should only be
used if the build utilites are not provided by your distribution's package
management system, for example on Mac OS.
jhbuild build [--autogen] [--clean] [--dist] [--distcheck]
[--ignore-suggests] [--no-network] [--skip=module...]
[--start-at=module] [--tags=tags] [-D date] [--no-xvfb]
[--try-checkout] [--no-poison] [--force] [--build-optional-modules]
[--min-age=time] [module...]
The build command builds one or more packages, including their
dependencies.
If no module names are provided on the command line, the modules
list from the configuration file will be used.
-a, --autogen
Always run autogen.sh before building modules. By default,
autogen.sh will only be called if the top-level makefile is
missing. Otherwise, JHBuild relies on the package's makefiles to
detect if configure needs to be rebuilt or rerun.
-c, --clean
Run make clean before building modules.
-d, --dist
Run make dist after building modules.
--distcheck
Run make distcheck after building modules.
--ignore-suggests
Do not build soft dependencies.
-n, --no-network
Do not access the network when building modules. This will skip
download or update stages in a build. If a module can't be built
without network access, the module build will fail.
-s, --skip=module,...
Do not build the listed modules. Used to skip the building of
specified dependencies.
--tags=tag,...
Ignore modules that do not match tag. Modules are automatically
attributed a tag matching the name of the module's module set.
-t, --start-at=module
Start at the named module rather than at the beginning of the
list. This option is useful if the build was interrupted.
-D date
If supported by the underlying version control system, update the
source tree to the specified date before building. An ISO date
format is required, e.g. "2009-09-18 02:32Z".
-x, --no-xvfb
Run graphical tests on the actual X server rather than in a
simulated Xvfb.
-C, --try-checkout
If the build fails, and if supported by the version control system,
force a checkout and run autogen.sh before retrying the build.
-N, --no-poison
If one or more of a module's dependencies failed, this option forces
JHBuild to try to build the module anyway.
-f, --force
Build the modules even if policy states it is not required.
--build-optional-modules
Modules listed as optional dependencies, may not be required to
build the module. This option forces JHBuild to build optional
dependencies.
--min-age=time
Skip modules installed more recently than the specified relative
time. The time string format is a number followed by a unit. The
following units are supported: seconds (s), minutes (m), hours (h)
and days (d). For example, --min-age=2h will skip modules built
less than two hours ago.
jhbuild buildone [--autogen] [--clean] [--distcheck] [--no-network]
[-D date] [--no-xvfb] [--force] [--min-age=time] module...
The buildone command is similar to build, but it does not build the
dependent modules. It is useful for rebuilding one or more modules.
jhbuild sanitycheck
The sanitycheck command performs a number of checks to verify the
build environment is okay.
For details of all jbhuild's command line options:
jhbuild --help
Reporting Bugs
--------------
If you find any bugs in JHBuild, or have feature requests (or
implementations :), please file them at:
https://gitlab.gnome.org/GNOME/jhbuild/issues/new
This will ensure your request is not lost.