mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-16 23:05:42 +00:00
0d5d951951
The IDLManager in the moz.build backend is a bit weird. It maintains a bunch of per-IDL file information, some of which isn't used, and attempts to map module names to information about what entities the module needs to be built. The former is done with Python dicts, and the latter with Python tuples, both resulting in some contortions by the clients of IDLManager to specify exactly what they need. Let's clean this up, by making IDLManager to more clearly do two jobs: 1. Keep track of whether IDL files are globally unique; and 2. Map module names to the information needed to build them. In the case of #2, we store everything as a straight Python object, so we can use actual property accesses everywhere. We also provide a stems() function on IDLManager to make some client code more straightforward. Doing this makes IDLManager much more XPIDL module-centric, and paves the way for the same change to be made in the frontend as well. |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| l10n/fluent_migrations | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| safety | ||
| 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