Lines Matching full:variable
23 systems extend the functionality of the variable as it is
42 This variable can be defined to be used by the fetcher to authenticate
59 considerations surrounding this variable:
99 the checksum mechanism. A common example would be the variable for
141 variable, use the following form::
157 BB_DISKMON_WARNINTERVAL variable,
185 variable. This example causes the build system to immediately halt
188 directories are provided with the variable, the build system also
192 defined by the :term:`BB_DISKMON_WARNINTERVAL` variable.
206 If you are going to use the :term:`BB_DISKMON_WARNINTERVAL` variable, you
208 variable and define its action as "WARN". During the build,
212 If you do not provide a :term:`BB_DISKMON_WARNINTERVAL` variable and you
217 When specifying the variable in your configuration file, use the
249 this variable is not specified (which is the default), the following
255 You must set this variable in the external environment in order
266 You must set this variable in the external environment in order
278 ``my-recipe.bb`` is executing, the :term:`BB_FILENAME` variable contains
284 wishing to create a source mirror would want to enable this variable.
292 Setting this variable to "1" when :term:`BB_GIT_SHALLOW` is also set to
299 repositories. This separate variable exists so that shallow tarball
306 Setting this variable to "1" enables the support for fetching, using and
316 regardless of whether this variable is set or not. Support for shallow
336 When used with :term:`BB_GENERATE_SHALLOW_TARBALLS`, this variable sets
342 If this variable is unset, bitbake will default to a depth of 1 when
409 ``ConfigParsed`` event can set the variable to trigger the re-parse.
421 variable is undefined and the log filenames get created using the
427 variable in a configuration file.
437 this variable to suppress BitBake's warnings.
439 To use the variable, list provider names (e.g. recipe names,
464 rule of thumb is to set this variable to twice the number of cores.
468 was run. The copy is taken before any variable values configured to
474 The contents of this variable is a datastore object that can be
483 You must set this variable in the external environment in order
489 :term:`BB_RUNFMT` variable is undefined and the run filenames get
495 variable in a configuration file.
521 :term:`BB_SCHEDULER` variable.
530 The function specified by this variable returns a "True" or "False"
534 Lists variable flags (varflags) that can be safely excluded from
540 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:variable flags`"
555 :term:`BB_SRCREV_POLICY` variable is useful when working without a
558 The variable can be set using one of two policies:
568 this variable to a value causes BitBake to report an error if it
576 timeouts. You can use the :term:`BB_TASK_IONICE_LEVEL` variable to adjust
581 This variable works similarly to the :term:`BB_TASK_NICE_LEVEL`
582 variable except with a task's I/O priorities.
584 Set the variable as follows::
609 You can use this variable in combination with task overrides to raise
616 Within an executing task, this variable holds the hash of the task as
626 this variable to "1" when a task is being executed. The value is not
641 code, it usually is as simple as adding the variable to your recipe.
651 variants by rewriting variable values and applying overrides such
668 You must set this variable in the external environment in order
674 name to this variable in its ``conf/layer.conf`` file.
677 Variable that expands to match files from
679 variable is used in the ``conf/layer.conf`` file and must be suffixed
686 This variable is useful in situations where the same recipe appears
687 in more than one layer. Setting this variable allows you to
690 layers. The precedence established through this variable stands
691 regardless of a recipe's version (:term:`PV` variable).
696 A larger value for the :term:`BBFILE_PRIORITY` variable results in a
698 than the value 5. If not specified, the :term:`BBFILE_PRIORITY` variable
699 is set based on layer dependencies (see the :term:`LAYERDEPENDS` variable
722 Use the :term:`BBFILES_DYNAMIC` variable to avoid ``.bbappend`` files whose
772 Lists the layers to enable during the build. This variable is defined
794 You can use the :term:`BBMASK` variable to "hide" these ``.bb`` and
829 each separate configuration (multiconfig). You can use this variable
850 (``.conf``) files. This variable is analogous to the ``PATH``
851 variable.
855 Set the variable as you would any environment variable and then run
863 Points to the server that runs memory-resident BitBake. The variable
872 variable is equivalent to using the ``-u`` command-line option.
876 You must set this variable in the external environment in order
898 The most common usage of this is variable is to set it to "-1" within
900 variable in this way causes the stable version of the recipe to build
907 :term:`BBFILE_PRIORITY` if that variable is different between two
925 variable.
934 repositories, use the :term:`BB_GENERATE_MIRROR_TARBALLS` variable.
942 To exclude a recipe from a world build using this variable, set the
943 variable to "1" in the recipe.
954 environment. The :term:`FAKEROOT` variable is obsolete and has been
975 :term:`FAKEROOTBASEENV` variable.
981 :term:`FAKEROOTENV` variable.
986 variable (e.g. ``FETCHCMD_git`` or ``FETCHCMD_svn``).
989 Points at the current file. BitBake sets this variable during the
991 this variable when a recipe is being executed to identify the recipe
997 handling ``file://`` URLs. The variable behaves like a shell ``PATH``
998 environment variable. The value is a colon-separated list of
1032 You use this variable in the ``conf/layer.conf`` file. You must also
1033 use the specific layer name as a suffix to the variable (e.g.
1037 When used inside the ``layer.conf`` configuration file, this variable
1038 provides the path of the current layer. This variable is not
1043 When used inside the ``layer.conf`` configuration file, this variable
1046 variable is not available outside of ``layer.conf`` and references
1051 can use this variable within
1055 You use this variable in the ``conf/layer.conf`` file. You must also
1056 use the specific layer name as a suffix to the variable (e.g.
1094 :term:`PACKAGES_DYNAMIC` variable, but a package with the module name is
1098 The epoch of the recipe. By default, this variable is unset. The
1099 variable is used to make upgrades possible when the versioning scheme
1121 recipes provide the same item. You should always suffix the variable
1134 :term:`PREFERRED_PROVIDER`. However, the :term:`PREFERRED_PROVIDERS` variable
1146 If there are multiple versions of a recipe available, this variable
1148 suffix the variable with the :term:`PN` you want to
1152 The :term:`PREFERRED_VERSION` variable supports limited wildcard use
1225 Following is an example of how the :term:`PRSERV_HOST` variable is set::
1229 You must set the variable if you want to automatically start a local PR
1242 Because the :term:`RDEPENDS` variable applies to packages being built,
1243 you should always use the variable in a form with an attached package
1251 Thus, the :term:`RDEPENDS` variable has the ``${PN}-dev`` package name as part
1252 of the variable.
1257 with the :term:`RDEPENDS` variable::
1275 variable.
1282 If there are multiple versions of a recipe available, this variable
1298 variable in conjunction with a package name override. Here is an
1308 the :term:`RDEPENDS` variable.
1313 with the :term:`RRECOMMENDS` variable::
1334 The list of source files --- local or remote. This variable tells
1341 variable that specifies all those sources.
1363 variable. Thus, the build system searches, in order, from the
1436 The date of the source code used to build the package. This variable
1442 variable applies only when using Subversion, Git, Mercurial and
1455 and these are referenced in the :term:`SRCREV_FORMAT` variable. Consider
1469 :term:`STAMP` variable, :term:`STAMPCLEAN` can contain
1488 variable.