Mirror Sites: If fetch failures occur, BitBake next uses mirror Source URI: If pre-mirrors fail, BitBake uses the original URL (e.g Pre-mirror Sites: BitBake first uses pre-mirrors to try and find URLs by looking for source files in a specific search order: When the download() method is called, BitBake tries to resolve the
TORTOISEHG WEB SERVER EXECUTABLE CODE
(sstate) code uses the fetch module to fetch the sstate files. In OpenEmbedded for example, the shared state The SRC_URI and WORKDIR variables are not hardcoded into theįetcher, since those fetcher methods can be (and are) called withĭifferent variable names. If you want to see the above code in action,Įxamine the OpenEmbedded class file base.bbclass The code to execute the first part of this process, a fetch, looksįor convenience, the naming in these examples matches the variables
Patching, however, is not covered by this module. GettingĪnd unpacking the files is often optionally followed by patching. The files from somewhere (cached or otherwise) and then unpacking thoseįiles into a specific location and perhaps in a specific way. Theįetcher codebase deals with two distinct processes in order: obtaining 4.1 The Download (Fetch) īitBake takes several steps when fetching source code or files. “fetch” refers to “fetch2” in this manual. Obsolete and has been removed from the codebase. It is the second major version of the API. The current fetch module is called “fetch2” and refers to the fact that As such, this module forms an important part of BitBake. Fetching source code is one of the cornerstones of building With the intricacies of downloading source code and files from remote
BitBake’s fetch module is a standalone piece of library code that deals
0 kommentar(er)
