Lines Matching +full:fetch +full:- +full:depth
1 .. SPDX-License-Identifier: CC-BY-2.5
17 - The variables listed in this glossary are specific to BitBake.
20 - Also, variables exist in other systems that use BitBake (e.g. The
34 In OpenEmbedded-Core, :term:`ASSUME_PROVIDED` mostly specifies native
35 tools that should not be built. An example is ``git-native``, which
37 rather than building ``git-native``.
41 :ref:`Azure Storage fetcher <bitbake-user-manual/bitbake-user-manual-fetching:fetchers>`
43 and gain access to non-public artifacts.
46 AZ_SAS = ""se=2021-01-01&sp=r&sv=2018-11-09&sr=c&skoid=<skoid>&sig=<signature>""
49 https://docs.microsoft.com/en-us/azure/storage/common/storage-sas-overview
57 Specifies a space-delimited list of hosts that the fetcher is allowed
61 - This host list is only used if
65 - Limited support for the "``*``" wildcard character for matching
83 - Mirrors not in the host list are skipped and logged in debug.
85 - Attempts to access networks not in the host list cause a failure.
94 a successful fetch from the :term:`PREMIRRORS` occurs.
118 condition often occurs when layers get out of sync (e.g. ``oe-core``
128 The default task to use when none is specified (e.g. with the ``-c``
278 ``my-recipe.bb`` is executing, the :term:`BB_FILENAME` variable contains
279 "/foo/path/my-recipe.bb".
307 …r tarballs of `shallow git repositories <https://riptutorial.com/git/example/4584/shallow-clone>`_.
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
313 try to fetch the full mirror tarball and use that.
338 With a depth of 1, only the commit referenced in :term:`SRCREV` is
339 included in the shallow mirror tarball. Increasing the depth includes
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
368 want to exclude when checking whether or not to re-parse and thus
388 the ``bin/bitbake-hashserv`` script provided by BitBake,
390 to start the server in read-only mode, to avoid accepting
408 re-parsing the base metadata (i.e. all the recipes). The
409 ``ConfigParsed`` event can set the variable to trigger the re-parse.
415 :ref:`bitbake-user-manual/bitbake-user-manual-execution:logging`
506 - *basic* --- the basic framework from which everything derives. Using
510 - *speed* --- executes tasks first that have more tasks depending on
513 - *completion* --- causes the scheduler to try to complete a given
540 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:variable flags`"
560 - *cache* --- retains the value the system obtained previously rather
563 - *clear* --- queries the source controls system every time. With this
567 Sets a more strict checksum mechanism for non-local URLs. Setting
569 encounters a non-local URL that does not have at least one checksum
604 $ sudo sh -c "echo cfq > /sys/block/device/queu/scheduler"
633 OpenEmbedded-Core metadata are "natives" such as ``quilt-native``,
635 such as ``gcc-cross``, which is a compiler built to run on the build
643 OpenEmbedded-Core metadata::
652 as ``_class-native``. For example, to generate a native version of
654 rewritten to a :term:`DEPENDS` on "foo-native".
664 incremented by the ``-D`` command line option.
689 --- effectively letting you control the precedence for the multiple
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
739 clang-layer:${LAYERDIR}/bbappends/meta-clang/*/*/*.bbappend \
740 core:${LAYERDIR}/bbappends/openembedded-core/meta/*/*/*.bbappend \
747 !clang-layer:${LAYERDIR}/backfill/meta-clang/*/*/*.bb \
754 /work/my-layer/bbappends/meta-security-isafw/*/*/*.bbappend
755 /work/my-layer/bbappends/openembedded-core/meta/*/*/*.bbappend
758 Contains a space-separated list of all of all files that BitBake's
778 /home/scottrif/poky/meta-yocto \
779 /home/scottrif/poky/meta-yocto-bsp \
780 /home/scottrif/poky/meta-mykernel \
783 This example enables four layers, one of which is a custom, user-defined
784 layer named ``meta-mykernel``.
788 in conjunction with ``bitbake-layers layerindex-fetch`` and tells
789 ``bitbake-layers`` where to place the fetched layers.
808 ``meta-ti/recipes-misc/`` directory::
810 BBMASK = "meta-ti/recipes-misc/"
816 BBMASK += "/meta-ti/recipes-misc/ meta-ti/recipes-ti/packagegroup/"
817 BBMASK += "/meta-oe/recipes-support/"
818 BBMASK += "/meta-foo/.*/openldap"
845 … ":ref:`bitbake-user-manual/bitbake-user-manual-intro:executing a multiple configuration build`"
863 Points to the server that runs memory-resident BitBake. The variable
864 is only used when you employ memory-resident BitBake.
868 command-line target recipes you want to build.
872 variable is equivalent to using the ``-u`` command-line option.
898 The most common usage of this is variable is to set it to "-1" within
911 Lists a recipe's build-time dependencies (i.e. other recipe files).
961 bitbake-worker process in the fakeroot environment.
964 Contains the command that starts the bitbake-worker process in the
985 fetch operations. You need to use an override suffix when you use the
998 environment variable. The value is a colon-separated list of
999 directories that are searched left-to-right in order.
1020 … ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:\`\`inherit\`\` configuration directive`"
1077 ":ref:`bitbake-user-manual/bitbake-user-manual-metadata:conditional syntax
1110 revision numbers (i.e. ``eglibc-2.13-r20+svnr15508/`` and
1111 ``bash-4.2-r1/``).
1126 PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto"
1127 PREFERRED_PROVIDER_virtual/xserver = "xserver-xf86"
1159 PREFERRED_VERSION_linux-yocto = "4.12%"
1248 RDEPENDS:${PN}-dev += "perl"
1251 Thus, the :term:`RDEPENDS` variable has the ``${PN}-dev`` package name as part
1274 For information on build-time dependencies, see the :term:`DEPENDS`
1278 The directory in which a local copy of a ``google-repo`` directory is
1297 As with all package-controlling variables, you must always use the
1301 RPROVIDES:${PN} = "widget-abi-2"
1334 The list of source files --- local or remote. This variable tells
1336 example, if the recipe or append file needs to fetch a single tarball
1339 append file needs to fetch a tarball, apply two patches, and include
1347 the :ref:`bitbake-user-manual/bitbake-user-manual-fetching:fetchers`
1350 - ``az://``: Fetches files from an Azure Storage account using HTTPS.
1352 - ``bzr://``: Fetches files from a Bazaar revision control
1355 - ``ccrc://``: Fetches files from a ClearCase repository.
1357 - ``cvs://``: Fetches files from a CVS revision control
1360 - ``file://``: Fetches files, which are usually files shipped
1368 - ``${BPN}``: the base recipe name without any special suffix
1371 - ``${BP}`` - ``${BPN}-${PV}``: the base recipe name and
1374 - ``files``: files within a directory, which is named ``files``
1377 - ``ftp://``: Fetches files from the Internet using FTP.
1379 - ``git://``: Fetches files from a Git revision control
1382 - ``gitsm://``: Fetches submodules from a Git revision control
1385 - ``hg://``: Fetches files from a Mercurial (``hg``) revision
1388 - ``http://``: Fetches files from the Internet using HTTP.
1390 - ``https://``: Fetches files from the Internet using HTTPS.
1392 - ``npm://``: Fetches JavaScript modules from a registry.
1394 - ``osc://``: Fetches files from an OSC (OpenSUSE Build service)
1397 - ``p4://``: Fetches files from a Perforce (``p4``) revision
1400 - ``repo://``: Fetches files from a repo (Git) repository.
1402 - ``ssh://``: Fetches files from a secure shell.
1404 - ``svn://``: Fetches files from a Subversion (``svn``) revision
1409 - ``downloadfilename``: Specifies the filename used when storing
1412 - ``name``: Specifies a name to be used for association with
1424 - ``subdir``: Places the file (or extracts its contents) into the
1429 - ``subpath``: Limits the checkout to a specific subpath of the
1432 - ``unpack``: Controls whether or not to unpack the file if it is