Lines Matching full:bitbake
9 BitBake files have their own syntax. The syntax has similarities to
76 occurs, you can use BitBake to check the actual value of the suspect
82 $ bitbake -e
86 ``local.conf``, ``bblayers.conf``, ``bitbake.conf`` and so forth)
97 $ bitbake recipename -e | grep VARIABLENAME=\"
105 Outside of :ref:`functions <bitbake-user-manual/bitbake-user-manual-metadata:functions>`,
106 BitBake joins any line ending in
128 BitBake does not interpret escape sequences like "\\n" in variable
165 :ref:`bitbake-user-manual/bitbake-user-manual-metadata:immediate variable
323 BitBake-style Python functions. See the ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:she…
335 When you use this syntax, BitBake expects one or more strings.
393 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:conditional syntax (overrides)`" section.
398 Variable flags are BitBake's implementation of variable properties or
401 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:variable flags`" section.
420 documentation to a BitBake variable as follows::
435 variables from BitBake's internal data dictionary, ``d``. The following
457 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:anonymous python functions`" section.
463 BitBake's internal data dictionary by using the "unset" keyword. Here is
474 When specifying pathnames for use with BitBake, do not use the tilde
476 cause BitBake to not recognize the path since BitBake does not expand
501 BitBake does not expand ``$ENV_VARIABLE`` in this case because it lacks the
512 In the output of ``bitbake -e``, variables that are exported to the
521 BitBake uses :term:`OVERRIDES` to control what
522 variables are overridden after BitBake parses recipes and configuration
572 - *Appending and Prepending:* BitBake also supports append and prepend
590 - *Setting a Variable for a Single Task:* BitBake supports setting a
613 Before BitBake 1.52 (Honister 3.4), the syntax for :term:`OVERRIDES`
624 Key expansion happens when the BitBake datastore is finalized. To better
631 In this case, after all the parsing is complete, BitBake expands
704 operators are affecting the order of assignments as BitBake passes
707 these assignments are made, BitBake applies the ":append" operations.
713 BitBake allows for metadata sharing through include files (``.inc``) and
721 This section presents the mechanisms BitBake provides to allow you to
729 BitBake uses the :term:`BBPATH` variable to locate
730 needed include and class files. Additionally, BitBake searches the
737 In order for include and class files to be found by BitBake, they need
746 BitBake only supports this directive when used within recipe and class
761 In this case, BitBake would search for the directory
776 :ref:`include <bitbake-user-manual/bitbake-user-manual-metadata:\`\`include\`\` directive>` and :re…
813 BitBake understands the ``include`` directive. This directive causes
814 BitBake to parse whatever file you specify, and to insert that file at
817 BitBake locates the first file it can find within :term:`BBPATH`.
820 functionality as compared to the :ref:`inherit <bitbake-user-manual/bitbake-user-manual-metadata:\`…
844 BitBake understands the ``require`` directive. This directive behaves
845 just like the ``include`` directive with the exception that BitBake
852 :ref:`inherit <bitbake-user-manual/bitbake-user-manual-metadata:\`\`inherit\`\` directive>` directi…
857 Similar to how BitBake handles :ref:`include <bitbake-user-manual/bitbake-user-manual-metadata:\`\`…
858 the path specified on the require line is a relative path, BitBake
877 class. BitBake only supports this directive when used within a
892 Because .conf files are parsed first during BitBake's execution, using
907 to build up operations into tasks. BitBake supports these types of
914 - *BitBake-Style Python Functions:* Functions written in Python and
915 executed by BitBake or other Python functions using
978 function, not just :ref:`tasks <bitbake-user-manual/bitbake-user-manual-metadata:tasks>`.
980 You can use the ``bitbake -e recipename`` command to view the final
983 BitBake-Style Python Functions
986 These functions are written in Python and executed by BitBake or other
989 An example BitBake function is::
1010 override-style operators to BitBake-style Python functions.
1032 You can use the ``bitbake -e recipename`` command to view
1058 - The BitBake datastore is not automatically available. Consequently,
1064 BitBake-Style Python Functions Versus Python Functions
1067 Following are some important differences between BitBake-style Python
1070 - Only BitBake-style Python functions can be :ref:`tasks <bitbake-user-manual/bitbake-user-manual-…
1073 BitBake-style Python functions.
1077 - :ref:`Variable flags <bitbake-user-manual/bitbake-user-manual-metadata:variable flags>` such as
1078 ``[dirs]``, ``[cleandirs]``, and ``[lockfiles]`` can be used on BitBake-style
1081 - BitBake-style Python functions generate a separate
1091 BitBake-style Python functions are usually tasks and are called
1092 directly by BitBake, but can also be called manually from Python code
1119 BitBake-style Python functions unless you need a feature specific to
1120 BitBake-style Python functions. Regular Python functions in metadata are
1121 a more recent invention than BitBake-style Python functions, and older
1184 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:functions you can call from within python`"
1186 the ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:inline python variable expansion`" sect…
1191 Through coding techniques and the use of ``EXPORT_FUNCTIONS``, BitBake
1257 Tasks are BitBake execution units that make up the steps that BitBake
1265 Tasks are either :ref:`shell functions <bitbake-user-manual/bitbake-user-manual-metadata:shell func…
1266 :ref:`BitBake-style Python functions <bitbake-user-manual/bitbake-user-manual-metadata:bitbake-styl…
1285 by the ``bitbake`` command unless another task is specified explicitly).
1295 ``bitbake``
1296 command. This is because BitBake considers the task "up-to-date"
1298 rerun for experimentation purposes, you can make BitBake always
1300 :ref:`[nostamp] <bitbake-user-manual/bitbake-user-manual-metadata:Variable Flags>`
1308 $ bitbake recipe -c printdate -f
1310 When manually selecting a task to run with the bitbake ``recipe
1321 explicitly selecting it with ``bitbake`` recipe ``-c printdate``. You
1325 $ bitbake recipe -c listtasks
1328 ":ref:`bitbake-user-manual/bitbake-user-manual-execution:dependencies`" section.
1330 See the ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:variable flags`" section for inform…
1372 When running a task, BitBake tightly controls the shell execution
1378 By default, BitBake cleans the environment to include only those
1386 #. Tell BitBake to load what you want from the environment into the
1392 the environment variable ``CCACHE_DIR`` to BitBake's passthrough
1397 #. Tell BitBake to export what you have loaded into the datastore to the
1409 A side effect of the previous steps is that BitBake records the
1416 original execution environment. BitBake saves a copy of the original
1434 dependencies. BitBake reads and writes varflags to the datastore using
1443 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:variable flag syntax`" section for details.
1445 BitBake has a defined set of varflags available for recipes and classes.
1455 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:inter-task
1459 …:term:`DEPENDS` variable and the ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:build dep…
1477 - ``[nostamp]``: When set to "1", tells BitBake to not generate a
1515 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:inter-task dependencies`" section for
1521 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:runtime dependencies`" section for more
1531 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:recursive dependencies`" section for
1542 ":ref:`bitbake-user-manual/bitbake-user-manual-execution:checksums (signatures)`" section.
1548 does not allow BitBake to automatically determine that the variable
1555 - ``[vardepvalue]``: If set, instructs BitBake to ignore the actual
1566 BitBake allows installation of event handlers within recipe and class
1612 consists of ``bitbake.conf``, ``base.bbclass`` and any global
1627 - ``bb.event.ParseStarted()``: Fired when BitBake is about to start
1629 of recipes BitBake plans to parse.
1639 - ``bb.event.BuildStarted()``: Fired when a new build starts. BitBake
1650 - ``bb.build.TaskInvalid()``: Fired if BitBake tries to execute a task
1663 - ``bb.cooker.CookerExit()``: Fired when the BitBake server/cooker
1669 information from the BitBake server to other parts of BitBake such as
1687 BitBake supports multiple incarnations of a recipe file via the
1708 To allow for efficient parallel processing, BitBake handles dependencies
1730 BitBake uses the ``addtask`` directive to manage dependencies that are
1751 …checksum <bitbake-user-manual/bitbake-user-manual-execution:checksums (signatures)>` has changed s…
1759 $ bitbake recipe -c mytask
1768 BitBake uses the :term:`DEPENDS` variable to manage
1782 BitBake uses the :term:`PACKAGES`, :term:`RDEPENDS`, and :term:`RRECOMMENDS`
1797 runtime dependency namespace, BitBake knows how to map them back
1803 BitBake uses the ``[recrdeptask]`` flag to manage recursive task
1804 dependencies. BitBake looks through the build-time and runtime
1807 BitBake has accomplished this, it recursively works through the
1821 BitBake allows a task to recursively depend on itself by
1830 case BitBake will ignore the current recipe's ``do_a``
1836 BitBake uses the ``[depends]`` flag in a more generic form to manage
1852 BitBake provides many functions you can call from within Python
1859 It is often necessary to access variables in the BitBake datastore using
1860 Python functions. The BitBake datastore has an API that allows you this
1921 ``bitbake/lib/bb``. For example, ``bitbake/lib/bb/utils.py`` includes
1928 BitBake uses checksums (or signatures) along with the setscene to
1930 To help understand how BitBake does this, the section assumes an
1934 examine the checksums using the following BitBake command::
1936 $ bitbake-dumpsigs
1941 ``bitbake-dumpsigs`` allows you to examine the ``do_compile`` task's
1954 Specifies a function BitBake calls that determines whether BitBake