Lines Matching full:variables

66 The ``layer.conf`` files are used to construct key variables such as
80 variables, including:
88 The first four variables in this list relate to how BitBake treats shell
89 environment variables during task execution. By default, BitBake cleans
90 the environment variables and provides tight control over the shell
92 variables, you can apply your control regarding the environment
93 variables allowed to be used by BitBake in the shell during execution of
96 section and the information about these variables in the variable
107 set the :term:`BBPATH` and :term:`BBFILES` variables directly in the
114 variables correctly for a given build directory.
122 ``.conf`` files. Some variables directly influence BitBake's behavior.
123 These variables might have been set from the environment depending on
124 the environment variables previously mentioned or set in the
125 configuration files. The ":ref:`bitbake-user-manual/bitbake-user-manual-ref-variables:Variables Glo…
127 variables.
194 various variables into the datastore.
208 are used to set the variables :term:`PN` and
366 Dependencies are defined through several variables. You can find
367 information about variables BitBake uses in the
368 :doc:`bitbake-user-manual-ref-variables` near the end of this manual. At a
371 :term:`RDEPENDS` variables when calculating
436 exported variables, and the shell functions with all variables expanded.
450 variables that control the behavior:
481 to define a list of variables that should never be included when
493 process needs to figure out what variables a Python function accesses
537 in a list of global variable dependency excludes --- variables never
538 included in any checksum. This example uses variables from OpenEmbedded