gecko-dev

История

Mike Hommey 14c1084f72 Bug 1679938 - Don't recurse the build into mfbt for projects that don't need it. r=firefox-build-system-reviewers,mhentges While all toolkit and js-based projects make use of mfbt, some others, like tools/crashreporter and tools/update-packaging, don't. So instead of including mfbt from the top-level directory, include it from the relevant project top-level mozbuilds. This allows to remove the dependency on mfbt files in the hash for the minidump-stackwalk and mar-tools toolchains. Differential Revision: https://phabricator.services.mozilla.com/D98378		2020-12-01 23:52:03 +00:00
..
README	…
app.mozbuild	Bug 1679938 - Don't recurse the build into mfbt for projects that don't need it. r=firefox-build-system-reviewers,mhentges	2020-12-01 23:52:03 +00:00
confvars.sh	…
moz.configure	Bug 1654103: Standardize on Black for Python code in `mozilla-central`.	2020-10-26 18:34:53 +00:00

README

This directory defines a build project for focused work on the "update
programs": programs owned or maintained by the Install/Update team
that are standalone binaries (i.e., not part of the Firefox binary
proper).

To use this build project, prepare a minimal mozconfig with
```
ac_add_options --enable-project=tools/update-programs
```

Depending on the mozconfig options and host and target OS, some of the
following will be built:

1. the maintenance service (when `--enable-maintenance-service`);
2. the updater binary (when `MOZ_UPDATER=1`);
3. the Windows Default Browser Agent (when `--enable-default-browser-agent`);
4. the Background Update Agent (when `--enable-update-agent`).

Packaging the installer and uninstaller is not yet supported: instead,
use an (artifact) build with `--enable-application=browser`.