зеркало из https://github.com/mozilla/gecko-dev.git
ac5b6e6cd0
Since the test goes through all moz.build files disregarding DIRS and the conditions that may disable directories, in some cases, moz.builds can fail to be evaluated properly because of missing variables in config.status. This time (because it's not the first), it's LLVM_DLLTOOL. After fixing that, it turns out many of the files/directories pointed to by Files() directives were removed or moved. While here, make the test script python3-ready. Differential Revision: https://phabricator.services.mozilla.com/D70157 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| gdbpp/gdbpp | ||
| l10n | ||
| lldbutils | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozperftest | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| safety | ||
| README | ||
| 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