Lines Matching refs:URL

66 -  *Source URI:* If pre-mirrors fail, BitBake uses the original URL (e.g
72 For each URL passed to the fetcher, the fetcher calls the submodule that
73 handles that particular URL type. This behavior can be the source of
80 In the former case, the URL is passed to the ``wget`` fetcher, which does not
159 A number of parameters exist that you can specify within the URL to
162 -  *unpack:* Controls whether the URL components are unpacked. If set to
173 -  *subdir:* Unpacks the specific URL to the specified subdirectory
191 As mentioned earlier, the URL prefix determines which fetcher submodule
192 BitBake uses. Each submodule can support different URL parameters, which
201 you specify within the URL can be either an absolute or relative path to
245    Because URL parameters are delimited by semi-colons, this can
260    (W3C). Note that due to the nature of the URL, you may have to
290 As well as the standard username and password URL syntax, you can also
291 configure the fetcher with various URL parameters:
369    username is different than the username used in the main URL, which
401      When ``protocol`` is "ssh", the URL expected in :term:`SRC_URI` differs
403      by the Git server to fetch from. For example, the URL returned by GitLab
405      ``git@gitlab.freedesktop.org:mesa/mesa.git``, however the expected URL in
413    unpacking when set to "1". Set this option for the URL where there is
580 in order to define the Perforce server URL and port, username, and
584 the server's URL and port number, and you can specify a username and
587 Here is an example that relies on ``P4CONFIG`` to specify the server URL
595 Here is an example that specifies the server URL and port, username, and
685 Here is an example URL::
705 Here is an example URL::
735 Here is an example URL with both fetchers::
746 to automatically create a recipe from an NPM URL.