Lines Matching full:bitbake
9 This chapter lists common variables used by BitBake and gives an
17 - The variables listed in this glossary are specific to BitBake.
20 - Also, variables exist in other systems that use BitBake (e.g. The
30 Lists recipe names (:term:`PN` values) BitBake does not
31 attempt to build. Instead, BitBake assumes these recipes have already
41 :ref:`Azure Storage fetcher <bitbake-user-manual/bitbake-user-manual-fetching:fetchers>`
53 The directory in which BitBake executes functions during a recipe's
100 the path of the build. BitBake's output should not (and usually does
108 Specifies the path to a log file into which BitBake's user interface
116 Defines how BitBake handles situations where an append file
239 These variables cause BitBake to
248 the external environment into BitBake's datastore. If the value of
260 external environment into BitBake's datastore. This list of variables
270 When set to "1", causes BitBake's fetcher module to only search
271 :term:`PREMIRRORS` for files. BitBake will not
287 repositories is not the default action by BitBake. ::
293 "1" causes bitbake to generate shallow mirror tarballs when fetching git
298 enabled, bitbake will generate shallow mirror tarballs by default for git
308 … The external `git-make-shallow <https://git.openembedded.org/bitbake/tree/bin/git-make-shallow>`_
311 When :term:`BB_GIT_SHALLOW` is enabled, bitbake will attempt to fetch a shallow
342 If this variable is unset, bitbake will default to a depth of 1 when
365 One of the ways BitBake determines whether to re-parse the main
371 not exclude them, BitBake would never reuse the cache.
376 If set to ``auto``, BitBake automatically starts its own server
380 If set to ``unix://path``, BitBake will connect to an existing
383 If set to ``host:port``, BitBake will connect to a remote server on the
388 the ``bin/bitbake-hashserv`` script provided by BitBake,
415 :ref:`bitbake-user-manual/bitbake-user-manual-execution:logging`
430 Allows you to suppress BitBake warnings caused when building two
433 BitBake normally issues a warning when building two different recipes
437 this variable to suppress BitBake's warnings.
443 Allows BitBake to run at a specific priority (i.e. nice level).
444 System permissions usually mean that BitBake can reduce its priority
449 Disables network access in the BitBake fetcher modules. With this
458 Sets the number of threads BitBake uses when parsing. By default, the
462 The maximum number of tasks BitBake should run in parallel at any one
467 Contains a copy of the original external environment in which BitBake
469 pass through from the external environment are filtered into BitBake's
479 from the external environment into BitBake's datastore.
504 BitBake tasks. Three options exist:
524 Specifies a function BitBake calls that determines whether BitBake
527 When running a setscene task, BitBake needs to know which
540 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:variable flags`"
544 Defines the name of the signature handler BitBake uses. The signature
568 this variable to a value causes BitBake to report an error if it
620 Controls how verbose BitBake is during builds. If set, shell scripts
625 Specifies if the current context is executing a task. BitBake sets
663 Sets the BitBake debug output level to a specific value as
706 You can use the command bitbake-layers show-layers to list all
710 A space-separated list of recipe files BitBake uses to build
758 Contains a space-separated list of all of all files that BitBake's
788 in conjunction with ``bitbake-layers layerindex-fetch`` and tells
789 ``bitbake-layers`` where to place the fetched layers.
792 Prevents BitBake from processing recipes and recipe append files.
795 ``.bbappend`` files. BitBake ignores any recipe or recipe append
796 files that match any of the expressions. It is as if BitBake does not
798 otherwise used by BitBake.
807 BitBake to ignore all recipe and recipe append files in the
828 Enables BitBake to perform multiple configuration builds and lists
830 to cause BitBake to build multiple targets where each target has a
845 … ":ref:`bitbake-user-manual/bitbake-user-manual-intro:executing a multiple configuration build`"
849 Used by BitBake to locate class (``.bbclass``) and configuration
853 If you run BitBake from a directory outside of the build directory,
856 BitBake::
860 $ bitbake target
863 Points to the server that runs memory-resident BitBake. The variable
864 is only used when you employ memory-resident BitBake.
871 Used to specify the UI module to use when running BitBake. Using this
888 Specifies the directory BitBake uses to store a cache of the metadata
889 so it does not need to be parsed every time BitBake is started.
937 Directs BitBake to exclude a recipe from world builds (i.e.
938 ``bitbake world``). During world builds, BitBake locates, parses and
961 bitbake-worker process in the fakeroot environment.
964 Contains the command that starts the bitbake-worker process in the
984 Defines the command the BitBake fetcher module executes when running
989 Points at the current file. BitBake sets this variable during the
990 parsing process to identify the file being parsed. BitBake also sets
995 Specifies directories BitBake uses when searching for patches and
1020 … ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:\`\`inherit\`\` configuration directive`"
1029 this case). BitBake produces an error if any dependency is missing or
1063 Specifies additional paths from which BitBake gets source code. When
1071 BitBake uses :term:`OVERRIDES` to control what variables are overridden
1072 after BitBake parses recipes and configuration files.
1077 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:conditional syntax
1103 Specifies the directory BitBake uses to store data that should be
1105 that uses BitBake's persistent data API and the data used by the PR
1172 Specifies additional paths from which BitBake gets source code. When
1254 BitBake supports specifying versioned dependencies. Although the
1255 syntax varies depending on the packaging format, BitBake hides these
1310 BitBake supports specifying versioned recommends. Although the syntax
1311 varies depending on the packaging format, BitBake hides these
1335 BitBake which bits to pull for the build and how to pull them. For
1344 protocols are highly dependent on particular BitBake Fetcher
1345 submodules. Depending on the fetcher BitBake uses, various URL
1347 the :ref:`bitbake-user-manual/bitbake-user-manual-fetching:fetchers`
1444 performing a query on the remote repository every time BitBake parses
1471 remove. BitBake uses a clean operation to remove any other stamps it
1482 Points to a directory were BitBake places temporary files, which
1487 Points to the build directory. BitBake automatically sets this