author Cameron McCormack <>
Tue, 14 Jan 2014 09:24:22 +1100
changeset 179235 481e4766030eefc867a29701d37007c3796e696b
parent 163157 0d9f5e4bd5b8789fe2f516972844d76c520c8077
child 453478 4f1a5068af92d329781d4805519a0904c45d0e67
permissions -rw-r--r--
Bug 959016 - Add lldb Python command handlers for debugging Gecko, starting with frametree and frametreelimited. (DONTBUILD) r=ehsan


.. glossary::

   object directory
       A directory holding the output of the build system. The build
       system attempts to isolate all file modifications to this
       directory. By convention, object directories are commonly
       directories under the source directory prefixed with **obj-**.
       e.g. **obj-firefox**.

       A shell script used to configure the build system.

       A generated shell script which detects the current system
       environment, applies a requested set of build configuration
       options, and writes out metadata to be consumed by the build

       An executable file produced by **configure** that takes the
       generated build config and writes out files used to build the
       tree. Traditionally, config.status writes out a bunch of

   install manifest
       A file containing metadata describing file installation rules.
       A large part of the build system consists of copying files
       around to appropriate places. We write out special files
       describing the set of required operations so we can process the
       actions effeciently. These files are install manifests.

   clobber build
      A build performed with an initially empty object directory. All
      build actions must be performed.

   incremental build
      A build performed with the result of a previous build in an
      object directory. The build should not have to work as hard because
      it will be able to reuse the work from previous builds.

      An API for accessing a common and limited subset of the build and
      run-time configuration. See :ref:`mozinfo`.