build/docs/glossary.rst@97036ab72558 (annotated)
build/docs/glossary.rst
Tue, 06 Jan 2015 21:39:09 +0100
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Tue, 06 Jan 2015 21:39:09 +0100
- branch
- TOR_BUG_9701
- changeset 8
- 97036ab72558
- permissions
- -rw-r--r--
Conditionally force memory storage according to privacy.thirdparty.isolate;
This solves Tor bug #9701, complying with disk avoidance documented in
https://www.torproject.org/projects/torbrowser/design/#disk-avoidance.
| michael@0 | 1 | ======== |
| michael@0 | 2 | Glossary |
| michael@0 | 3 | ======== |
| michael@0 | 4 | |
| michael@0 | 5 | .. glossary:: |
| michael@0 | 6 | :sorted: |
| michael@0 | 7 | |
| michael@0 | 8 | object directory |
| michael@0 | 9 | A directory holding the output of the build system. The build |
| michael@0 | 10 | system attempts to isolate all file modifications to this |
| michael@0 | 11 | directory. By convention, object directories are commonly |
| michael@0 | 12 | directories under the source directory prefixed with **obj-**. |
| michael@0 | 13 | e.g. **obj-firefox**. |
| michael@0 | 14 | |
| michael@0 | 15 | mozconfig |
| michael@0 | 16 | A shell script used to configure the build system. |
| michael@0 | 17 | |
| michael@0 | 18 | configure |
| michael@0 | 19 | A generated shell script which detects the current system |
| michael@0 | 20 | environment, applies a requested set of build configuration |
| michael@0 | 21 | options, and writes out metadata to be consumed by the build |
| michael@0 | 22 | system. |
| michael@0 | 23 | |
| michael@0 | 24 | config.status |
| michael@0 | 25 | An executable file produced by **configure** that takes the |
| michael@0 | 26 | generated build config and writes out files used to build the |
| michael@0 | 27 | tree. Traditionally, config.status writes out a bunch of |
| michael@0 | 28 | Makefiles. |
| michael@0 | 29 | |
| michael@0 | 30 | install manifest |
| michael@0 | 31 | A file containing metadata describing file installation rules. |
| michael@0 | 32 | A large part of the build system consists of copying files |
| michael@0 | 33 | around to appropriate places. We write out special files |
| michael@0 | 34 | describing the set of required operations so we can process the |
| michael@0 | 35 | actions effeciently. These files are install manifests. |
| michael@0 | 36 | |
| michael@0 | 37 | clobber build |
| michael@0 | 38 | A build performed with an initially empty object directory. All |
| michael@0 | 39 | build actions must be performed. |
| michael@0 | 40 | |
| michael@0 | 41 | incremental build |
| michael@0 | 42 | A build performed with the result of a previous build in an |
| michael@0 | 43 | object directory. The build should not have to work as hard because |
| michael@0 | 44 | it will be able to reuse the work from previous builds. |
| michael@0 | 45 | |
| michael@0 | 46 | mozinfo |
| michael@0 | 47 | An API for accessing a common and limited subset of the build and |
| michael@0 | 48 | run-time configuration. See :ref:`mozinfo`. |
