mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-06-04 02:00:04 +00:00
Code Issues Projects Releases Wiki Activity

Documentation: poky-ref-manual - Updated STAMPS directory information

Browse Source 
The STAMPS directory is now structured as
build/tmp/stamps/$MULTIMACH_TARGET_SYS/<extended_PN>/$PV.
There were three areas in the manual that needed adjusting
to reflect this change.

(From yocto-docs rev: 1f8d64ecfa8e060680a90f9c6cc5f69554328da5)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2012-12-10 16:47:27 -06:00
committed by Richard Purdie
parent 0173d4e10d
commit 044a8f9e6a
3 changed files with 11 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/poky-ref-manual/ref-bitbake.xml
+2 -3
View File
@@ -219,9 +219,8 @@
<para> <para>
As each task completes, a timestamp is written to the directory specified by the As each task completes, a timestamp is written to the directory specified by the
<filename><link linkend='var-STAMP'>STAMP</link></filename> variable (usually <filename><link linkend='var-STAMP'>STAMP</link></filename> variable.
<filename>build/tmp/stamps/*/</filename>). On subsequent runs, BitBake looks within the <filename>/build/tmp/stamps</filename>
On subsequent runs, BitBake looks at the <filename>/build/tmp/stamps</filename>
directory and does not rerun directory and does not rerun
tasks that are already completed unless a timestamp is found to be invalid. tasks that are already completed unless a timestamp is found to be invalid.
Currently, invalid timestamps are only considered on a per Currently, invalid timestamps are only considered on a per
documentation/poky-ref-manual/ref-structure.xml
+8 -3
View File
@@ -422,9 +422,14 @@
<para> <para>
This directory holds information that BitBake uses for accounting purposes This directory holds information that BitBake uses for accounting purposes
to track what tasks have run and when they have run. to track what tasks have run and when they have run.
The directory is sub-divided by architecture. The directory is sub-divided by architecture, package name, and
The files in the directory are empty of data. version.
However, BitBake uses the filenames and timestamps for tracking purposes. Following is an example:
<literallayout class='monospaced'>
stamps/all-poky-linux/distcc-config/1.0-r0.do_build-2fdd....2do
</literallayout>
Although the files in the directory are empty of data,
BitBake uses the filenames and timestamps for tracking purposes.
</para> </para>
</section> </section>
documentation/poky-ref-manual/ref-variables.xml
+1 -1
View File
@@ -2766,7 +2766,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
as set in the <filename>meta/conf/bitbake.conf</filename> file as set in the <filename>meta/conf/bitbake.conf</filename> file
is: is:
<literallayout class='monospaced'> <literallayout class='monospaced'>
STAMP = "${TMPDIR}/stamps/${MULTIMACH_TARGET_SYS}/${PN}-${EXTENDPE}${PV}-${PR}" STAMP = "${TMPDIR}/stamps/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}"
</literallayout> </literallayout>
See <link linkend='var-TMPDIR'><filename>TMPDIR</filename></link>, See <link linkend='var-TMPDIR'><filename>TMPDIR</filename></link>,
<link linkend='var-MULTIMACH_TARGET_SYS'><filename>MULTIMACH_TARGET_SYS</filename></link>, <link linkend='var-MULTIMACH_TARGET_SYS'><filename>MULTIMACH_TARGET_SYS</filename></link>,