mirror of
https://repo.dactyloidae.xyz/Dactyloidae/UXP.git
synced 2026-10-18 13:17:29 +09:00
import FIREFOX_52_6_0esr_RELEASE from mozilla-esr52 hg repo
This commit is contained in:
commit
dcd9973243
150858 changed files with 23884658 additions and 0 deletions
38
build/docs/mozbuild/dumbmake.rst
Normal file
38
build/docs/mozbuild/dumbmake.rst
Normal file
|
|
@ -0,0 +1,38 @@
|
|||
dumbmake
|
||||
========
|
||||
|
||||
*dumbmake* is a simple dependency tracker for make.
|
||||
|
||||
It turns lists of make targets into longer lists of make targets that
|
||||
include dependencies. For example:
|
||||
|
||||
netwerk, package
|
||||
|
||||
might be turned into
|
||||
|
||||
netwerk, netwerk/build, toolkit/library, package
|
||||
|
||||
The dependency list is read from the plain text file
|
||||
`topsrcdir/build/dumbmake-dependencies`. The format best described by
|
||||
example:
|
||||
|
||||
build_this
|
||||
when_this_changes
|
||||
|
||||
Interpret this to mean that `build_this` is a dependency of
|
||||
`when_this_changes`. More formally, a line (CHILD) indented more than
|
||||
the preceding line (PARENT) means that CHILD should trigger building
|
||||
PARENT. That is, building CHILD will trigger building first CHILD and
|
||||
then PARENT.
|
||||
|
||||
This structure is recursive:
|
||||
|
||||
build_this_when_either_change
|
||||
build_this_only_when
|
||||
this_changes
|
||||
|
||||
This means that `build_this_when_either_change` is a dependency of
|
||||
`build_this_only_when` and `this_changes`, and `build_this_only_when`
|
||||
is a dependency of `this_changes`. Building `this_changes` will build
|
||||
first `this_changes`, then `build_this_only_when`, and finally
|
||||
`build_this_when_either_change`.
|
||||
41
build/docs/mozbuild/index.rst
Normal file
41
build/docs/mozbuild/index.rst
Normal file
|
|
@ -0,0 +1,41 @@
|
|||
========
|
||||
mozbuild
|
||||
========
|
||||
|
||||
mozbuild is a Python package providing functionality used by Mozilla's
|
||||
build system.
|
||||
|
||||
Modules Overview
|
||||
================
|
||||
|
||||
* mozbuild.backend -- Functionality for producing and interacting with build
|
||||
backends. A build backend is an entity that consumes build system metadata
|
||||
(from mozbuild.frontend) and does something useful with it (typically writing
|
||||
out files that can be used by a build tool to build the tree).
|
||||
* mozbuild.compilation -- Functionality related to compiling. This
|
||||
includes managing compiler warnings.
|
||||
* mozbuild.frontend -- Functionality for reading build frontend files
|
||||
(what defines the build system) and converting them to data structures
|
||||
which are fed into build backends to produce backend configurations.
|
||||
* mozpack -- Functionality related to packaging builds.
|
||||
|
||||
Overview
|
||||
========
|
||||
|
||||
The build system consists of frontend files that define what to do. They
|
||||
say things like "compile X" "copy Y."
|
||||
|
||||
The mozbuild.frontend package contains code for reading these frontend
|
||||
files and converting them to static data structures. The set of produced
|
||||
static data structures for the tree constitute the current build
|
||||
configuration.
|
||||
|
||||
There exist entities called build backends. From a high level, build
|
||||
backends consume the build configuration and do something with it. They
|
||||
typically produce tool-specific files such as make files which can be used
|
||||
to build the tree.
|
||||
|
||||
Piecing it all together, we have frontend files that are parsed into data
|
||||
structures. These data structures are fed into a build backend. The output
|
||||
from build backends is used by builders to build the tree.
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue