Lines Matching full:example
22 The following example sets ``VARIABLE`` to "value". This assignment
109 variable assignments over multiple lines, as in the following example::
119 Consider this additional example where the two assignments both assign
152 of the referenced variables. The following example should clarify this
169 exist, the string is kept as is. For example, given the following
181 if the variable has a value. Here is an example::
201 any previously defined weak default value. Here is an example::
251 In this example, ``A`` contains "test 123", even though the final value
336 Surrounding spaces and spacing are preserved. Here is an example::
359 override style operators provide guaranteed operations. For example,
388 example to use "+=" would be to add a space before "baz" in the
428 an example::
432 This example results in the ``DATE`` variable being set to the current date.
464 an example::
479 Instead, provide a fuller path as the following example illustrates::
489 the ``export`` keyword. For example, in the following example, the
508 variable. Here is an example::
545 non-conditional version. Here is an example::
552 In this example, the :term:`OVERRIDES`
558 To better understand this, consider a practical example that assumes
574 listed in :term:`OVERRIDES`. Here is an example::
580 In this example, :term:`DEPENDS` becomes "glibc ncurses libmad".
583 example, the following lines will conditionally append to the
591 variable just for the duration of a single task. Here is an example::
597 previous example, ``FOO`` has the value "val 1" while the
607 "``:prepend``") as shown in the following example::
615 using ``_append``, ``_prepend``, and ``_remove``, for example.
625 understand this, consider the following example::
651 example::
668 This next example changes the order of the override and the append::
680 This next example has the order of the appends and overrides reversed
681 back as in the first example::
695 This final example mixes in some varying operators::
714 class files (``.bbclass``). For example, suppose you have a piece of
751 example, you can easily abstract out the tasks involved in building a
755 As an example, your recipes could use the following directive to inherit
770 them with spaces. The following example shows how to inherit both the
779 statement. Here is an example::
791 Another method is by using anonymous Python. Here is an example::
826 As an example, suppose you needed a recipe to include some self-test
861 As an example, suppose you have two versions of a recipe (e.g.
880 As an example, suppose you needed to inherit a class file called
898 separate the classes. The following example shows how to inherit both
932 functions. Here is an example shell function definition::
949 As an example, consider the following::
989 An example BitBake function is::
1012 As an example, consider the following::
1041 is an example::
1093 by using the ``bb.build.exec_func()`` function. Here is an example::
1114 exception. For example, an exception raised by ``bb.fatal()`` will be caught
1130 of parsing. For example, the following conditionally sets a variable
1144 recipe. As an example, consider the following snippet::
1158 The previous example is conceptually
1172 before anonymous functions run. In the following example, ``FOO`` ends
1214 For example, if you have a class file
1225 For example, continuing with
1226 the same example, the statement in the ``bar.bbclass`` would be as
1232 Continuing with the same example, if your recipe needs to call the
1269 the task and other tasks. Here is an example that shows how to define a
1283 In the previous example, the ``do_printdate`` task becomes a dependency
1292 If you try out the previous example, you might see that the
1315 without specifying any dependencies as is done in the following example::
1319 In this example, assuming dependencies have not been
1323 as shown in the following example::
1336 dependencies when calling ``addtask``. For example, here's a snippet
1348 ``deltask`` command to delete a task. For example, to delete the example
1354 dependencies, the dependencies are not reconnected. For example, suppose
1390 example, assume you want to prevent the build system from accessing
1421 ``getVar(, False)``. The datastore object is useful, for example, to
1422 find the original ``DISPLAY`` variable. Here is an example::
1427 The previous example returns ``BAR`` from the original execution
1494 Set the value globally. For example, the following makes sure the
1535 task's stamp. As an example, OpenEmbedded uses this flag to allow
1547 for example, when a function refers to a variable in a manner that
1573 Following is an example event handler that prints the name of the event
1585 In the previous example, an eventmask has been
1596 For example, "BuildStarted" and "BuildCompleted" events run before any
1667 This next list of example events occur based on specific requests to the
1691 to "extend" the recipe for each variant. Here is an example that results in a
1733 depend on that recipe. Here is an example::
1737 In this example, the ``do_printdate`` task
1771 that task can be executed. Here is an example::
1775 In this example, the ``do_populate_sysroot`` task
1794 example, the ``do_packagedata`` task of each item in :term:`RDEPENDS` must
1812 that need to wait for some task to finish "globally". For example,
1839 data in :term:`DEPENDS`. Here is an example::
1843 In this example, the ``do_populate_sysroot`` task of the target ``quilt-native``
1913 example, ``d.expand("foo ${X}")`` expands to the literal string "foo
1921 ``bitbake/lib/bb``. For example, ``bitbake/lib/bb/utils.py`` includes
1931 OpenEmbedded metadata-based example.
1940 build system generates signatures. For example, using
1971 which it is used. For example, some variables and filenames allow