зеркало из https://github.com/mozilla/gecko-dev.git
8748a005b3
The recursivemake backend knows how to do several things with the IPDL sources: 1) Determine the C++ sources that will be generated from given IPDL sources. 2) Write out all the makefile rules and variables for said sources. The first part isn't unique to the recursivemake backend; other backends would eventually like to know what C++ sources come from IPDL source files for easier cross-referencing purposes, etc. Let's take a first cut at moving things into CommonBackend. (This may not be the best interface, since it relies on consume_finished being invoked, and not all backends call CommonBackend.consume_finished. Still, it's a start.) |
||
|---|---|---|
| .. | ||
| bitstring | ||
| blessings | ||
| configobj | ||
| eme | ||
| jsmin | ||
| lldbutils | ||
| mach | ||
| mock-1.0.0 | ||
| mozboot | ||
| mozbuild | ||
| mozversioncontrol/mozversioncontrol | ||
| psutil | ||
| pyasn1 | ||
| virtualenv | ||
| which | ||
| 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: * 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