blob: 1befca9ec193353ffe82a995a2002616da8ca7dd (
plain)
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
|
.. _mozconfig:
===============
mozconfig Files
===============
mozconfig files are used to configure how a build works.
mozconfig files are actually shell scripts. They are executed in a
special context with specific variables and functions exposed to them.
API
===
Functions
---------
The following special functions are available to a mozconfig script.
ac_add_options
^^^^^^^^^^^^^^
This function is used to declare extra options/arguments to pass into
configure.
e.g.::
ac_add_options --disable-tests
ac_add_options --enable-optimize
mk_add_options
^^^^^^^^^^^^^^
This function is used to inject statements into client.mk for execution.
It is typically used to define variables, notably the object directory.
e.g.::
mk_add_options AUTOCLOBBER=1
ac_add_options
^^^^^^^^^^^^^^
This is a variant of ac_add_options() which only adds configure options
for a specified application. This is only used when building multiple
applications through client.mk. This function is typically not needed.
Special mk_add_options Variables
--------------------------------
For historical reasons, the method for communicating certain
well-defined variables is via mk_add_options(). In this section, we
document what those special variables are.
MOZ_OBJDIR
^^^^^^^^^^
This variable is used to define the :term:`object directory` for the current
build.
Finding the active mozconfig
============================
Multiple mozconfig files can exist to provide different configuration
options for different tasks. The rules for finding the active mozconfig
are defined in the
:py:func:`mozbuild.mozconfig.MozconfigLoader.find_mozconfig` method:
.. autoclass:: mozbuild.mozconfig.MozconfigLoader
:members: find_mozconfig
|
