mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-27 14:52:16 +00:00
d6cbf36fe7
This patch: 1. Produces additional frameworks as part of every build. In compile builds, the frameworks are built; in artifact builds, the frameworks binaries are taken from fetched artifacts. It's not easy to compile the same framework twice in the `moz.build` DSL, so some file shuffling is done in `Makefile.in` files to arrange the correct layout. 2. Packages and uploads a new `macos_framework_artifacts` extra archive for artifact builds to consume. 3. Consumes the new extra archive in artifact builds. Produced frameworks live in `$(topobjdir)/macos_framework_artifacts/xyz.framework/**`. Consumed frameworks are made availabe to artifact builds in `$(distdir)/macos_framework_artifacts`. Bug 1885985 - Part 2: Differential Revision: https://phabricator.services.mozilla.com/D205936 |
||
---|---|---|
.. | ||
docs | ||
gdbpp/gdbpp | ||
l10n | ||
lldbutils | ||
mach | ||
mozboot | ||
mozbuild | ||
mozlint | ||
mozperftest | ||
mozrelease | ||
mozterm | ||
mozversioncontrol | ||
sites | ||
mach_commands.py | ||
moz.build | ||
README |
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025