mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-16 23:05:42 +00:00
31e67ea398
The current IDL build setup assumes that all IDL files can be found in a single directory. This setup requires that all IDL files be copied to a single directory, which is suboptimal in terms of disk I/O and also complicates things like generating IDL files at build time. As a first step in moving away from this state of affairs, xpidl-process.py needs to be taught that the input IDL files could potentially be found in multiple directories. The current setup can just specify $(DIST)/idl as the lone directory to examine. Future patches will change this to examine multiple directories. |
||
---|---|---|
.. | ||
devtools/migrate-l10n | ||
docs | ||
l10n/fluent_migrations | ||
mach | ||
mozboot | ||
mozbuild | ||
mozlint | ||
mozrelease | ||
mozterm | ||
mozversioncontrol | ||
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