diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-12-10 18:39:59 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-12-11 16:17:57 +0000 |
commit | 45915123a727f86b106da7ccb761b23067b1ff88 (patch) | |
tree | 784421976c4feaa042713701a1a9ab423aeb85c9 /documentation/poky-ref-manual/usingpoky.xml | |
parent | 044a8f9e6a0cb5ffe0e97e62403bd077628e9924 (diff) | |
download | poky-45915123a727f86b106da7ccb761b23067b1ff88.tar.gz |
Documentation: poky-ref-manual - Updates to WORKDIR structure
The file structure beneath WORKDIR has changed such that
PN and PV are now separate directories. This affected several
areas in poky-ref-manual.
(From yocto-docs rev: 52b033c2c9e5aaa1f03072dd16c21a9d59a87150)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/poky-ref-manual/usingpoky.xml')
-rw-r--r-- | documentation/poky-ref-manual/usingpoky.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml index 286b5fa783..149490969a 100644 --- a/documentation/poky-ref-manual/usingpoky.xml +++ b/documentation/poky-ref-manual/usingpoky.xml | |||
@@ -123,7 +123,7 @@ | |||
123 | <filename>${WORKDIR}/temp/log.do_taskname.pid</filename>. | 123 | <filename>${WORKDIR}/temp/log.do_taskname.pid</filename>. |
124 | For example, the <filename>compile</filename> task for the QEMU minimal image for the x86 | 124 | For example, the <filename>compile</filename> task for the QEMU minimal image for the x86 |
125 | machine (<filename>qemux86</filename>) might be | 125 | machine (<filename>qemux86</filename>) might be |
126 | <filename>tmp/work/qemux86-poky-linux/core-image-minimal-1.0-r0/temp/log.do_compile.20830</filename>. | 126 | <filename>tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_compile.20830</filename>. |
127 | To see what BitBake runs to generate that log, look at the corresponding | 127 | To see what BitBake runs to generate that log, look at the corresponding |
128 | <filename>run.do_taskname.pid</filename> file located in the same directory. | 128 | <filename>run.do_taskname.pid</filename> file located in the same directory. |
129 | </para> | 129 | </para> |