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
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
|
Building Firefox On Windows
===========================
This document will help you get set up to build Firefox on your own
computer. Getting set up can take a while - we need to download a
lot of bytes! Even on a fast connection, this can take ten to fifteen
minutes of work, spread out over an hour or two.
If you'd prefer to build Firefox for Windows in a virtual machine,
you may be interested in the `Windows images provided by Microsoft
<https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/>`_.
Requirements
------------
- **Memory:** 4GB RAM minimum, 8GB+ recommended.
- **Disk Space:** At least 40GB of free disk space.
- **Operating System:** Windows 10. It is advisable to have Windows Update be fully
up-to-date. See :ref:`build_hosts` for more information.
1. System preparation
---------------------
1.1 Install Visual Studio Build Tools
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
`Download and install the Build Tools for Visual Studio 2022
<https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022>`_.
If you have a full install of Visual Studio (Community/Professional/Enterprise),
that is also supported.
Ensure you've checked the following items for installation:
- In the Workloads tab:
- Desktop development with C++.
- In the Individual components tab:
- MSVC v143 - VS 2022 C++ x64/x86 build tools.
- Windows 10 SDK (at least **10.0.19041.0**).
- C++ ATL for v143 build tools (x86 and x64).
.. note::
The recommended Visual Studio version and components has recently changed. If you run
into unexpected build errors, you should `report a bug
<https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox%20Build%20System&component=General>`_
or ask about it in the ``#build`` Matrix channel - the solution may be to downgrade back to
`Visual Studio 2019 <https://docs.microsoft.com/en-ca/visualstudio/releases/2019/release-notes>`_.
1.2 Install MozillaBuild
~~~~~~~~~~~~~~~~~~~~~~~~
Install `MozillaBuild
<https://ftp.mozilla.org/pub/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe>`_.
Accept the default installation directory.
Windows may prompt you to "reinstall with the correct settings", which you
should click to accept.
When working with Firefox tooling, you'll need to do so from within the MozillaBuild
shell. You can start it by running ``C:\mozilla-build\start-shell.bat`` (you may want
to make a shortcut to this file so it's easier to start).
.. note::
The MozillaBuild shell is a lot more like a Linux shell than the Windows ``cmd``. You can
learn more about it `here <https://wiki.mozilla.org/MozillaBuild>`_.
2. Bootstrap a copy of the Firefox source code
----------------------------------------------
Now that your system is ready, we can download the source code and have Firefox
automatically download the other dependencies it needs. The below command
will download a lot of data (years of Firefox history!) then guide you through
the interactive setup process.
.. code-block:: shell
cd c:/
mkdir mozilla-source
cd mozilla-source
wget https://hg.mozilla.org/mozilla-central/raw-file/default/python/mozboot/bin/bootstrap.py
python3 bootstrap.py
.. note::
When running ``bootstrap.py`` there will be a `UAC (User Account Control) prompt <https://docs.microsoft.com/en-us/windows/security/identity-protection/user-account-control/how-user-account-control-works>`_ for PowerShell after
selecting the destination directory for the source code clone. This is
necessary to add the Microsoft Defender Antivirus exclusions automatically. You
should select ``Yes`` on the UAC prompt, otherwise you will need
to :ref:`follow some manual steps below <Ensure antivirus exclusions>`.
.. note::
In general, the Firefox workflow works best with Mercurial. However,
if you'd prefer to use ``git``, you can grab the source code in
"git" form by running the bootstrap script with the ``vcs`` parameter:
.. code-block:: shell
python3 bootstrap.py --vcs=git
This uses `Git Cinnabar <https://github.com/glandium/git-cinnabar/>`_ under the hood.
Choosing a build type
~~~~~~~~~~~~~~~~~~~~~
If you aren't modifying the Firefox backend, then select one of the
:ref:`Artifact Mode <Understanding Artifact Builds>` options. If you are
building Firefox for Android, you should also see the :ref:`GeckoView Contributor Guide`.
.. _Ensure antivirus exclusions:
Ensure antivirus exclusions
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Microsoft Defender Antivirus and some third-party antivirus products
are known to significantly degrade build times and sometimes even cause failed
builds (due to a "missing file"). This is usually because we have tests for
well-known security bugs that have code samples that antivirus software identifies
as a threat, automatically quarantining/corrupting the files.
To avoid this, add the following folders to your third-party antivirus exclusion list:
- The ``C:\mozilla-build`` folder.
- The directory where the Firefox code is (probably ``C:\mozilla-source``).
- The ``%USERPROFILE%/.mozbuild`` directory (probably ``C:\Users\<user>\.mozbuild``).
The ``bootstrap.py`` script attempts to add the above folders to the Microsoft
Defender Antivirus exclusion list automatically. You should check that they were
successfully added, but if they're missing you will need to `add the exclusions to
Microsoft Defender Antivirus manually
<https://support.microsoft.com/en-ca/help/4028485/windows-10-add-an-exclusion-to-windows-security>`_.
.. note::
If you're already missing files (you'll see them listed in ``hg status``, you can have them
brought back by reverting your source tree: ``hg update -C``).
3. Build
--------
Now that your system is bootstrapped, you should be able to build!
.. code-block:: shell
cd c:/mozilla-source/mozilla-unified
hg up -C central
./mach build
./mach run
🎉 Congratulations! You've built your own home-grown Firefox!
Now the fun starts
------------------
Time to start hacking! You should join us on `Matrix <https://chat.mozilla.org/>`_,
say hello in the `Introduction channel
<https://chat.mozilla.org/#/room/#introduction:mozilla.org>`_, and `find a bug to
start working on <https://codetribute.mozilla.org/>`_.
See the :ref:`Firefox Contributors' Quick Reference` to learn how to test your changes,
send patches to Mozilla, update your source code locally, and more.
.. note::
If you'd like to interact with Mach from a different command line environment
than MozillaBuild, there's experimental support for it described
:ref:`over here <Using Mach on Windows Outside MozillaBuild>`.
Troubleshooting
---------------
MozillaBuild out-of-date
~~~~~~~~~~~~~~~~~~~~~~~~
The build system expects that you're using the most-recent MozillaBuild release.
However, MozillaBuild doesn't auto-update. If you're running into local issues,
they may be resolved by `upgrading your MozillaBuild <https://wiki.mozilla.org/MozillaBuild>`_.
Spaces in folder names
~~~~~~~~~~~~~~~~~~~~~~
**Firefox will not build** if the path to the installation
tool folders contains **spaces** or other breaking characters such as
pluses, quotation marks, or metacharacters. The Visual Studio tools and
SDKs are an exception - they may be installed in a directory which
contains spaces. It is strongly recommended that you accept the default
settings for all installation locations.
Installing Visual Studio in a different language than Windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If Visual Studio is using a different language than the system, then your build
may fail with a link error after reporting a bunch of include errors.
Quotation marks in ``PATH``
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Quotation marks (") aren't translated properly when passed to MozillaBuild
sub-shells. Since they're not usually necessary, you should ensure they're
not in your ``PATH`` environment variable.
``PYTHON`` environment variable
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If ``PYTHON`` is set, the build may fail with the error: "``The system
cannot find the file specified``." Ensure that you aren't having
a ``PYTHON`` environment variable set.
Cygwin interference
~~~~~~~~~~~~~~~~~~~
If you happen to have Cygwin installed, its tools may erroneously be
used when building Firefox. Ensure that MozillaBuild directories (in
``C:\mozilla-build\``) are before Cygwin directories in the ``PATH``
environment variable.
Building from within Users
~~~~~~~~~~~~~~~~~~~~~~~~~~
If you encounter a build failure with:
``LINK: fatal error LNK1181: cannot open input file ..\..\..\..\..\security\nss3.lib``
and the Firefox code is underneath the ``C:\Users`` folder, then you should try
moving the code to be underneath ``C:\\mozilla-source`` instead.
|
