summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/usingpoky.xml
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2013-04-04 14:33:29 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-10 15:20:53 (GMT)
commitea8e60842d77491c4d83c5d017e7b6d1920b950b (patch)
tree2b82549519bd855512127f0afddd03651dd68d90 /documentation/ref-manual/usingpoky.xml
parent67f4fd4ffa4144174f146e19f2c07a950168330d (diff)
downloadpoky-ea8e60842d77491c4d83c5d017e7b6d1920b950b.tar.gz
ref-manual: Applied Paul Eggleton's buildhistory patch 2 of 5.
Additional information added to the end of the "Build History Package Information" section." Buildhistory now collects information on SRCREV values for recipes fetched from a version control system e.g. Git; additionally a buildhistory-collect-srcrevs tool is provided to gather this and convert it to a format suitable for inclusion in global configuration. Add information on these new features to the appropriate section. (From yocto-docs rev: 8c38bcbe8e737d7dfb41a763c87a3a6269e6f980) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/usingpoky.xml')
-rw-r--r--documentation/ref-manual/usingpoky.xml52
1 files changed, 52 insertions, 0 deletions
diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml
index 3b0940f..677b5a2 100644
--- a/documentation/ref-manual/usingpoky.xml
+++ b/documentation/ref-manual/usingpoky.xml
@@ -545,6 +545,58 @@
545 busybox-staticdev busybox-locale 545 busybox-staticdev busybox-locale
546 </literallayout> 546 </literallayout>
547 </para> 547 </para>
548
549 <para>
550 Finally, for those recipes that are fetched from a version control
551 system (such as Git) there is a file that lists the source revision(s)
552 specified in the recipe and the actual revision used when building
553 (which may be different when <filename>SRCREV</filename> is set to
554 <filename>${AUTOREV}</filename> for example). Here is an example
555 of one of these files:
556 <filename>buildhistory/packages/emenlow-poky-linux/linux-yocto/latest_srcrev</filename>):
557 <literallayout class='monospaced'>
558 # SRCREV_machine = "b5c37fe6e24eec194bb29d22fdd55d73bcc709bf"
559 SRCREV_machine = "b5c37fe6e24eec194bb29d22fdd55d73bcc709bf"
560 # SRCREV_emgd = "caea08c988e0f41103bbe18eafca20348f95da02"
561 SRCREV_emgd = "caea08c988e0f41103bbe18eafca20348f95da02"
562 # SRCREV_meta = "c2ed0f16fdec628242a682897d5d86df4547cf24"
563 SRCREV_meta = "c2ed0f16fdec628242a682897d5d86df4547cf24"
564 </literallayout>
565 You can use the <filename>buildhistory-collect-srcrevs</filename>
566 command to collect the stored <filename>SRCREV</filename> values
567 from build history and report them in a format suitable for use in
568 global configuration (for example, local.conf or a distro include
569 file) to override floating AUTOREV values to a fixed set of revisions.
570 Here is some example output from this command:
571 <literallayout class='monospaced'>
572 # emenlow-poky-linux
573 SRCREV_machine_pn-linux-yocto = "b5c37fe6e24eec194bb29d22fdd55d73bcc709bf"
574 SRCREV_emgd_pn-linux-yocto = "caea08c988e0f41103bbe18eafca20348f95da02"
575 SRCREV_meta_pn-linux-yocto = "c2ed0f16fdec628242a682897d5d86df4547cf24"
576 # core2-poky-linux
577 SRCREV_pn-kmod = "62081c0f68905b22f375156d4532fd37fa5c8d33"
578 SRCREV_pn-blktrace = "d6918c8832793b4205ed3bfede78c2f915c23385"
579 SRCREV_pn-opkg = "649"
580 </literallayout>
581 Some notes on using the <filename>buildhistory-collect-srcrevs</filename>
582 command:
583 <itemizedlist>
584 <listitem><para>By default only values where the SRCREV was
585 not hardcoded (usually when AUTOREV was used) are reported
586 - use the <filename>-a</filename> option to see all SRCREV
587 values.</para></listitem>
588 <listitem><para>The output statements may not have any effect
589 in the face of overrides applied elsewhere in the build system
590 configuration; use the <filename>-f</filename> option to add the
591 <filename>forcevariable</filename> override to each output line
592 if you need to work around this.</para></listitem>
593 <listitem><para>The script does not do any special handling for
594 building for multiple machines; however it does place a
595 comment before each set of values specifying which triplet
596 (for example <filename>emenlow-poky-linux</filename>) that they
597 belong to as shown above.</para></listitem>
598 </itemizedlist>
599 </para>
548 </section> 600 </section>
549 601
550 <section id='build-history-image-information'> 602 <section id='build-history-image-information'>