@@ -43,11 +43,11 @@ In turn, the path to the work directory for the recipe
(:term:`WORKDIR`) is defined as
follows::
- ${TMPDIR}/work/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}
+ ${BASE_WORKDIR}/${MULTIMACH_TARGET_SYS}/${PN}/${PV}
The actual directory depends on several things:
-- :term:`TMPDIR`: The top-level build
+- :term:`BASE_WORKDIR`: The top-level build
output directory.
- :term:`MULTIMACH_TARGET_SYS`:
@@ -55,19 +55,13 @@ The actual directory depends on several things:
- :term:`PN`: The recipe name.
-- :term:`EXTENDPE`: The epoch --- if
- :term:`PE` is not specified, which is
- usually the case for most recipes, then :term:`EXTENDPE` is blank.
-
- :term:`PV`: The recipe version.
-- :term:`PR`: The recipe revision.
-
As an example, assume a Source Directory top-level folder named
-``poky``, a default :term:`Build Directory` at ``poky/build``, and a
+``project``, a default :term:`Build Directory` at ``project/build``, and a
``qemux86-poky-linux`` machine target system. Furthermore, suppose your
recipe is named ``foo_1.3.0.bb``. In this case, the work directory the
build system uses to build the package would be as follows::
- poky/build/tmp/work/qemux86-poky-linux/foo/1.3.0-r0
+ project/build/tmp/work/qemux86-poky-linux/foo/1.3.0
Fix the definition of WORKDIR to match OE-Core. Rename the Source Directory to "project" as part of the transition to bitbake-setup and the removal of Poky as in "the Poky repository". Reported-by: "Robert P. J. Day" <rpjday@crashcourse.ca> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> --- documentation/dev-manual/temporary-source-code.rst | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-)