Lines Matching refs:is
31 By default, this directory is ${WORKDIR}/${BPN}-${PV}, where ${BPN} is the
32 base recipe name and ${PV} is the recipe version. If the source tarball
34 the source code is fetched from an SCM such as Git or Subversion, then you
40 build system uses to keep the unpacked recipe for db is the following:
49 cloned to ${WORKDIR}/git during do_fetch. Since this path is different from the
81 directory is the same as the S directory, which is defined as:
98 builds a recipe. This directory is located within the TMPDIR directory
99 structure and is specific to the recipe being built and the system for which it
100 is being built.
102 The WORKDIR directory is defined as follows:
113 - **EXTENDPE**: The epoch — if PE is not specified, which is usually the
114 case for most recipes, then EXTENDPE is blank.
120 Furthermore, suppose your recipe is named foo_1.3.0-r0.bb. In this case, the
136 build system as input to create a package. The name is normally extracted from
137 the recipe file name. For example, if the recipe is named expat_2.0.1.bb, then
144 example, using bash to build packages for the native machine, PN is
153 The revision of the recipe. The default value for this variable is
156 PR is conventionally reset to "r0".
166 this case, PR, which is the default value of
168 package is the most recent one in cases where many packages have the
190 The version of the recipe. The version is normally extracted from the recipe
191 filename. For example, if the recipe is named expat_2.0.1.bb, then the default
192 value of PV will be “2.0.1”. PV is generally not overridden within a recipe
193 unless it is building an unstable (i.e. development) version from a source code
196 PV is the default value of the PKGV variable.