mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-24 13:21:05 +00:00
217bd35159
The way the processor works currently is that it relies on two different build backends, one of which produces json files for specific configurations, and the other which produces moz.build files from the aggregate of all those configs. Each of these json files is huge, and we actually don't have enough to support all the platforms we're supposed to be supporting. Adding more files is not enticing. Now that we've made the first step described above work in a single pass on a single machine (as opposed to multiple passes on multiple machines previously), we can actually merge both steps and avoid producing the intermediate json files altogether. This will allow to add more configurations without having to worry about the weight of those files. And because this all doesn't need to depend on having the first step hooked up in the build system, we make the whole an independent script rather than a build backend. Differential Revision: https://phabricator.services.mozilla.com/D149210 |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| 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