Lines Matching refs:term
29 :term:`ASSUME_PROVIDED`
30 Lists recipe names (:term:`PN` values) BitBake does not
34 In OpenEmbedded-Core, :term:`ASSUME_PROVIDED` mostly specifies native
39 :term:`AZ_SAS`
52 :term:`B`
56 :term:`BB_ALLOWED_NETWORKS`
62 :term:`BB_NO_NETWORK` is either not set or
87 Using :term:`BB_ALLOWED_NETWORKS` in conjunction with
88 :term:`PREMIRRORS` is very useful. Adding the
89 host you want to use to :term:`PREMIRRORS` results in the source code
92 :term:`SRC_URI` statement. This is because the
93 fetcher does not attempt to use the host listed in :term:`SRC_URI` after
94 a successful fetch from the :term:`PREMIRRORS` occurs.
96 :term:`BB_BASEHASH_IGNORE_VARS`
103 :term:`BB_CHECK_SSL_CERTS`
107 :term:`BB_CONSOLELOG`
111 :term:`BB_CURRENTTASK`
115 :term:`BB_DANGLINGAPPENDS_WARNONLY`
127 :term:`BB_DEFAULT_TASK`
132 :term:`BB_DEFAULT_UMASK`
136 :term:`BB_DISKMON_DIRS`
184 :term:`BB_DISKMON_WARNINTERVAL`
192 defined by the :term:`BB_DISKMON_WARNINTERVAL` variable.
203 :term:`BB_DISKMON_WARNINTERVAL`
206 If you are going to use the :term:`BB_DISKMON_WARNINTERVAL` variable, you
207 must also use the :term:`BB_DISKMON_DIRS`
212 If you do not provide a :term:`BB_DISKMON_WARNINTERVAL` variable and you
213 do use :term:`BB_DISKMON_DIRS` with the "WARN" action, the disk
246 :term:`BB_ENV_PASSTHROUGH`
250 list is used: :term:`BBPATH`, :term:`BB_PRESERVE_ENV`,
251 :term:`BB_ENV_PASSTHROUGH`, and :term:`BB_ENV_PASSTHROUGH_ADDITIONS`.
258 :term:`BB_ENV_PASSTHROUGH_ADDITIONS`
262 :term:`BB_ENV_PASSTHROUGH`.
269 :term:`BB_FETCH_PREMIRRORONLY`
271 :term:`PREMIRRORS` for files. BitBake will not
272 search the main :term:`SRC_URI` or
273 :term:`MIRRORS`.
275 :term:`BB_FILENAME`
278 ``my-recipe.bb`` is executing, the :term:`BB_FILENAME` variable contains
281 :term:`BB_GENERATE_MIRROR_TARBALLS`
283 to be placed in the :term:`DL_DIR` directory. Anyone
291 :term:`BB_GENERATE_SHALLOW_TARBALLS`
292 Setting this variable to "1" when :term:`BB_GIT_SHALLOW` is also set to
295 tarballs is controlled by :term:`BB_GIT_SHALLOW_DEPTH`.
297 If both :term:`BB_GIT_SHALLOW` and :term:`BB_GENERATE_MIRROR_TARBALLS` are
303 For example usage, see :term:`BB_GIT_SHALLOW`.
305 :term:`BB_GIT_SHALLOW`
311 When :term:`BB_GIT_SHALLOW` is enabled, bitbake will attempt to fetch a shallow
321 See also :term:`BB_GIT_SHALLOW_DEPTH` and
322 :term:`BB_GENERATE_SHALLOW_TARBALLS`.
335 :term:`BB_GIT_SHALLOW_DEPTH`
336 When used with :term:`BB_GENERATE_SHALLOW_TARBALLS`, this variable sets
338 With a depth of 1, only the commit referenced in :term:`SRCREV` is
345 For example usage, see :term:`BB_GIT_SHALLOW`.
347 :term:`BB_HASHCHECK_FUNCTION`
361 :term:`BB_HASHCONFIG_IGNORE_VARS`
373 :term:`BB_HASHSERVE`
378 to an upstream one, by setting :term:`BB_HASHSERVE_UPSTREAM`.
394 :term:`BB_HASHSERVE_UPSTREAM`
398 server is started (setting :term:`BB_HASHSERVE` to ``auto``),
406 :term:`BB_INVALIDCONF`
412 :term:`BB_LOGCONFIG`
418 :term:`BB_LOGFMT`
420 ``${``\ :term:`T`\ ``}``. By default, the :term:`BB_LOGFMT`
429 :term:`BB_MULTI_PROVIDER_ALLOWED`
442 :term:`BB_NICE_LEVEL`
445 but not raise it again. See :term:`BB_TASK_NICE_LEVEL` for
448 :term:`BB_NO_NETWORK`
457 :term:`BB_NUMBER_PARSE_THREADS`
461 :term:`BB_NUMBER_THREADS`
466 :term:`BB_ORIGENV`
477 :term:`BB_PRESERVE_ENV`
486 :term:`BB_RUNFMT`
488 saved into ``${``\ :term:`T`\ ``}``. By default, the
489 :term:`BB_RUNFMT` variable is undefined and the run filenames get
497 :term:`BB_RUNTASK`
502 :term:`BB_SCHEDULER`
516 :term:`BB_SCHEDULERS`
521 :term:`BB_SCHEDULER` variable.
523 :term:`BB_SETSCENE_DEPVALID`
533 :term:`BB_SIGNATURE_EXCLUDE_FLAGS`
543 :term:`BB_SIGNATURE_HANDLER`
552 :term:`BB_SRCREV_POLICY`
555 :term:`BB_SRCREV_POLICY` variable is useful when working without a
566 :term:`BB_STRICT_CHECKSUM`
572 :term:`BB_TASK_IONICE_LEVEL`
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`
606 :term:`BB_TASK_NICE_LEVEL`
615 :term:`BB_TASKHASH`
619 :term:`BB_VERBOSE_LOGS`
624 :term:`BB_WORKERCONTEXT`
630 :term:`BBCLASSEXTEND`
650 Internally, the :term:`BBCLASSEXTEND` mechanism generates recipe
653 a recipe, a :term:`DEPENDS` on "foo" is
654 rewritten to a :term:`DEPENDS` on "foo-native".
656 Even when using :term:`BBCLASSEXTEND`, the recipe is only parsed once.
662 :term:`BBDEBUG`
671 :term:`BBFILE_COLLECTIONS`
676 :term:`BBFILE_PATTERN`
678 :term:`BBFILES` in a particular layer. This
683 :term:`BBFILE_PRIORITY`
691 regardless of a recipe's version (:term:`PV` variable).
692 For example, a layer that has a recipe with a higher :term:`PV` value but
693 for which the :term:`BBFILE_PRIORITY` is set to have a lower precedence
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
709 :term:`BBFILES`
718 :term:`BBFILES_DYNAMIC`
722 Use the :term:`BBFILES_DYNAMIC` variable to avoid ``.bbappend`` files whose
731 Use the following form for :term:`BBFILES_DYNAMIC`::
757 :term:`BBINCLUDED`
761 :term:`BBINCLUDELOGS`
765 :term:`BBINCLUDELOGS_LINES`
766 If :term:`BBINCLUDELOGS` is set, specifies
768 reporting a failed task. If you do not set :term:`BBINCLUDELOGS_LINES`,
771 :term:`BBLAYERS`
786 :term:`BBLAYERS_FETCH_DIR`
791 :term:`BBMASK`
794 You can use the :term:`BBMASK` variable to "hide" these ``.bb`` and
827 :term:`BBMULTICONFIG`
831 separate configuration. Define :term:`BBMULTICONFIG` in your
843 For information on how to use :term:`BBMULTICONFIG` in an environment
848 :term:`BBPATH`
854 you must be sure to set :term:`BBPATH` to point to the build directory.
862 :term:`BBSERVER`
866 :term:`BBTARGETS`
870 :term:`BITBAKE_UI`
879 :term:`BUILDNAME`
883 :term:`BZRDIR`
887 :term:`CACHE`
891 :term:`CVSDIR`
895 :term:`DEFAULT_PREFERENCE`
901 by default in the absence of :term:`PREFERRED_VERSION` being used to
907 :term:`BBFILE_PRIORITY` if that variable is different between two
910 :term:`DEPENDS`
914 produce similarly named packages. In this example, the :term:`DEPENDS`
924 For information on runtime dependencies, see the :term:`RDEPENDS`
927 :term:`DESCRIPTION`
930 :term:`DL_DIR`
932 downloads. By default, :term:`DL_DIR` gets files suitable for mirroring for
934 repositories, use the :term:`BB_GENERATE_MIRROR_TARBALLS` variable.
936 :term:`EXCLUDE_FROM_WORLD`
947 Recipes added to :term:`EXCLUDE_FROM_WORLD` may still be built during a world
949 recipe to :term:`EXCLUDE_FROM_WORLD` only ensures that the recipe is not
952 :term:`FAKEROOT`
954 environment. The :term:`FAKEROOT` variable is obsolete and has been
958 :term:`FAKEROOTBASEENV`
960 by :term:`FAKEROOTCMD` that starts the
963 :term:`FAKEROOTCMD`
967 :term:`FAKEROOTDIRS`
971 :term:`FAKEROOTENV`
975 :term:`FAKEROOTBASEENV` variable.
977 :term:`FAKEROOTNOENV`
981 :term:`FAKEROOTENV` variable.
983 :term:`FETCHCMD`
988 :term:`FILE`
994 :term:`FILESPATH`
1001 :term:`GITDIR`
1005 :term:`HGDIR`
1009 :term:`HOMEPAGE`
1013 :term:`INHERIT`
1017 system ignores changes to :term:`INHERIT` in individual recipes.
1019 For more information on :term:`INHERIT`, see the
1023 :term:`LAYERDEPENDS`
1028 :term:`LAYERVERSION`\ ``_anotherlayer`` in
1036 :term:`LAYERDIR`
1042 :term:`LAYERDIR_RE`
1045 expression (:term:`BBFILE_PATTERN`). This
1049 :term:`LAYERVERSION`
1052 :term:`LAYERDEPENDS` for another layer in
1059 :term:`LICENSE`
1062 :term:`MIRRORS`
1066 locations defined by :term:`PREMIRRORS`, the
1067 upstream source, and then locations specified by :term:`MIRRORS` in that
1070 :term:`OVERRIDES`
1071 BitBake uses :term:`OVERRIDES` to control what variables are overridden
1076 find information on how to use :term:`OVERRIDES` in the
1080 :term:`P4DIR`
1084 :term:`PACKAGES`
1087 :term:`PACKAGES_DYNAMIC`
1090 :term:`PACKAGES_DYNAMIC` does not actually satisfy the dependencies, it
1092 runtime dependency (:term:`RDEPENDS`) of another
1094 :term:`PACKAGES_DYNAMIC` variable, but a package with the module name is
1097 :term:`PE`
1102 :term:`PERSISTENT_DIR`
1108 :term:`PF`
1113 :term:`PN`
1116 :term:`PR`
1119 :term:`PREFERRED_PROVIDER`
1123 :term:`PN` of the recipe to which you want to give
1130 :term:`PREFERRED_PROVIDERS`
1133 :term:`PREFERRED_PROVIDERS` is identical to
1134 :term:`PREFERRED_PROVIDER`. However, the :term:`PREFERRED_PROVIDERS` variable
1145 :term:`PREFERRED_VERSION`
1148 suffix the variable with the :term:`PN` you want to
1149 select, and you should set :term:`PV` accordingly for
1152 The :term:`PREFERRED_VERSION` variable supports limited wildcard use
1168 message will be shown. See :term:`REQUIRED_VERSION` if you want this
1171 :term:`PREMIRRORS`
1175 locations defined by :term:`PREMIRRORS`, the upstream source, and then
1176 locations specified by :term:`MIRRORS` in that order.
1193 :term:`PROVIDES`
1195 default, a recipe's own :term:`PN` is implicitly already in its
1196 :term:`PROVIDES` list. If a recipe uses :term:`PROVIDES`, the additional
1199 :term:`DEPENDS`.
1201 Consider the following example :term:`PROVIDES` statement from a recipe
1206 The :term:`PROVIDES` statement results in the "libav" recipe also being known
1210 :term:`PROVIDES` mechanism is also used to implement virtual targets. A
1213 functionality in question list the virtual target in :term:`PROVIDES`.
1215 virtual target in :term:`DEPENDS` to leave the
1222 :term:`PRSERV_HOST`
1223 The network based :term:`PR` service host and port.
1225 Following is an example of how the :term:`PRSERV_HOST` variable is set::
1230 service. You can set :term:`PRSERV_HOST` to other values to use a remote PR
1233 :term:`PV`
1236 :term:`RDEPENDS`
1242 Because the :term:`RDEPENDS` variable applies to packages being built,
1246 following :term:`RDEPENDS` statement::
1251 Thus, the :term:`RDEPENDS` variable has the ``${PN}-dev`` package name as part
1257 with the :term:`RDEPENDS` variable::
1274 For information on build-time dependencies, see the :term:`DEPENDS`
1277 :term:`REPODIR`
1281 :term:`REQUIRED_VERSION`
1283 determines which version should be given preference. :term:`REQUIRED_VERSION`
1284 works in exactly the same manner as :term:`PREFERRED_VERSION`, except
1288 If both :term:`REQUIRED_VERSION` and :term:`PREFERRED_VERSION` are set for
1289 the same recipe, the :term:`REQUIRED_VERSION` value applies.
1291 :term:`RPROVIDES`
1295 :term:`RDEPENDS`).
1303 :term:`RRECOMMENDS`
1308 the :term:`RDEPENDS` variable.
1313 with the :term:`RRECOMMENDS` variable::
1330 :term:`SECTION`
1333 :term:`SRC_URI`
1337 from the Internet, the recipe or append file uses a :term:`SRC_URI`
1340 a custom file, the recipe or append file needs an :term:`SRC_URI`
1362 The path is relative to the :term:`FILESPATH`
1413 :term:`SRC_URI` checksums or :term:`SRCREV` when you have more than one
1414 file or git repository specified in :term:`SRC_URI`. For example::
1435 :term:`SRCDATE`
1440 :term:`SRCREV`
1445 your recipe, you should specify a :term:`SRCREV` that is a full revision
1448 :term:`SRCREV_FORMAT`
1449 Helps construct valid :term:`SRCREV` values when
1451 :term:`SRC_URI`.
1454 circumstances. Each component in the :term:`SRC_URI` is assigned a name
1455 and these are referenced in the :term:`SRCREV_FORMAT` variable. Consider
1457 :term:`SRCREV_FORMAT` could look like "machine_meta" and those names
1462 :term:`STAMP`
1467 :term:`STAMPCLEAN`
1469 :term:`STAMP` variable, :term:`STAMPCLEAN` can contain
1474 :term:`SUMMARY`
1477 :term:`SVNDIR`
1481 :term:`T`
1486 :term:`TOPDIR`