mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
df3c4a7b92
The build system being what it currently is, there are various cases where one wants something explicit, rather than the current autodetection. For instance, one may want to run make -C $objdir chrome instead of make -C $objdir/chrome that mach build chrome currently invokes. There are several such usecases that mach's autodetection makes harder, and it's sometimes awkward when telling people, to debug their issues, to run make -C objdir something and hear back that objdir doesn't exist or something along those lines, because they took "objdir" literally. |
||
|---|---|---|
| .. | ||
| blessings | ||
| codegen | ||
| configobj | ||
| jsmin | ||
| lldbutils | ||
| mach | ||
| mock-1.0.0 | ||
| mozboot | ||
| mozbuild | ||
| mozversioncontrol/mozversioncontrol | ||
| psutil | ||
| virtualenv | ||
| which | ||
| 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