documentation/overview-manual/concepts.rst

207 The following figure shows an expanded representation of the "User
209 figure <overview-manual/concepts:openembedded build system concepts>`:
343 Configuration Edits" box in the figure.
370 figure <overview-manual/concepts:openembedded build system concepts>`:
381    "BSP Layer" in the following figure) providing machine-specific
389    the following figure) providing top-level or general policies for the
398 The following figure shows an expanded representation of these three
399 layers from the :ref:`general workflow figure
492    While the figure shows several
512 figure <overview-manual/concepts:openembedded build system concepts>`
514 Projects", and "SCMs (optional)" boxes. The figure represents mirrors,
550 area of the :ref:`general workflow figure <overview-manual/concepts:openembedded build system conce…
560 recipes. For example, the figure uses specific releases each for
624 :term:`Build Directory`. The :ref:`general workflow figure
688 figure <overview-manual/concepts:openembedded build system concepts>`,
734 variables. The preceding figure and the following list describe the
779    In the previous figure, notice that there are two sample hierarchies:
1107 actually install. For information on the variables listed in the figure,
1258 the :ref:`general workflow figure
1274 ``tmp/deploy/images/machine/`` folder as shown in the figure. This
1315 In the :ref:`general workflow figure
1355 shown in the previous figure. Depending on the type of SDK, there are
1438 The following figure shows a high-level build environment regarding
1497 need to cross-compile and test your software. The figure shows the
1675 process needs to figure out what variables a Python function accesses
1701 able to figure out dependencies. When running in debug mode (i.e. using
1703 it cannot figure out dependencies. The Yocto Project team has currently