summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/usingpoky.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-02-25 19:51:37 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-03-25 12:29:37 +0000
commit9953555002558f1abb1cd2d8143cf2be07c3171f (patch)
tree895208defb748de8ae338a75d920f30ff5cba687 /documentation/ref-manual/usingpoky.xml
parent89de0baf9c60711bed164e62355d384710316657 (diff)
downloadpoky-9953555002558f1abb1cd2d8143cf2be07c3171f.tar.gz
ref-manual: Edits to the "Maintaining Build Output Quality" section.
Removed the bit about isolating SDK information. Also removed the workaround and text regarding the limitation that caused adding and removing INHERIT += "buildhistory" to re-execute tasks. Added a few links to some newly documented variables. (From yocto-docs rev: 7d13bea6d9f0c2bdc9aa58c2933998d6d10ac810) 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.xml42
1 files changed, 8 insertions, 34 deletions
diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml
index 1d75a9994e..dd93f30dd1 100644
--- a/documentation/ref-manual/usingpoky.xml
+++ b/documentation/ref-manual/usingpoky.xml
@@ -475,7 +475,10 @@
475 475
476 <para> 476 <para>
477 Build history is disabled by default. 477 Build history is disabled by default.
478 To enable it, add the following statements to the end of your 478 To enable it, add the following <filename>INHERIT</filename>
479 statement and set the
480 <link linkend='var-BUILDHISTORY_COMMIT'><filename>BUILDHISTORY_COMMIT</filename></link>
481 variable to "1" at the end of your
479 <filename>conf/local.conf</filename> file found in the 482 <filename>conf/local.conf</filename> file found in the
480 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>: 483 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>:
481 <literallayout class='monospaced'> 484 <literallayout class='monospaced'>
@@ -496,25 +499,6 @@
496 <para> 499 <para>
497 You can disable build history by removing the previous statements 500 You can disable build history by removing the previous statements
498 from your <filename>conf/local.conf</filename> file. 501 from your <filename>conf/local.conf</filename> file.
499 However, you should realize that enabling and disabling
500 build history in this manner can change the
501 <filename>do_package</filename> task checksums which, if you
502 are using the OEBasicHash signature generator (the default
503 for many current distro configurations including
504 <filename>DISTRO = "poky"</filename> and
505 <filename>DISTRO = ""</filename>) will result in the packaging
506 tasks being re-run during the subsequent build.
507 </para>
508
509 <para>
510 To disable the build history functionality without causing the
511 packaging tasks to be re-run, set the
512 <link linkend='var-BUILDHISTORY_FEATURES'><filename>BUILDHISTORY_FEATURES</filename></link>
513 variable as follows in your <filename>conf/local.conf</filename>
514 file:
515 <literallayout class='monospaced'>
516 BUILDHISTORY_FEATURES = ""
517 </literallayout>
518 </para> 502 </para>
519 </section> 503 </section>
520 504
@@ -660,7 +644,7 @@
660 A directory containing selected files from the root 644 A directory containing selected files from the root
661 filesystem. 645 filesystem.
662 The files are defined by 646 The files are defined by
663 <filename>BUILDHISTORY_IMAGE_FILES</filename>. 647 <link linkend='var-BUILDHISTORY_IMAGE_FILES'><filename>BUILDHISTORY_IMAGE_FILES</filename></link>.
664 </para></listitem> 648 </para></listitem>
665 <listitem><para><filename>build-id:</filename> 649 <listitem><para><filename>build-id:</filename>
666 Human-readable information about the build configuration 650 Human-readable information about the build configuration
@@ -747,20 +731,9 @@
747 <title>Build History SDK Information</title> 731 <title>Build History SDK Information</title>
748 <para> 732 <para>
749 Build history collects similar information on the contents 733 Build history collects similar information on the contents
750 of SDKs (e.g., <filename>meta-toolchain</filename> 734 of SDKs (e.g. <filename>meta-toolchain</filename>
751 or <filename>bitbake -c populate_sdk imagename</filename>) 735 or <filename>bitbake -c populate_sdk imagename</filename>)
752 as compared to information it collects for images. 736 as compared to information it collects for images.
753 If you want information on the SDK, you need to list that
754 feature using the
755 <link linkend='var-BUILDHISTORY_FEATURES'><filename>BUILDHISTORY_FEATURES</filename></link>
756 variable as follows in your <filename>conf/local.conf</filename>
757 file found in the
758 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>:
759 <literallayout class='monospaced'>
760 INHERIT += "buildhistory"
761 BUILDHISTORY_COMMIT = "0"
762 BUILDHISTORY_FEATURES = "sdk"
763 </literallayout>:
764 The following list shows the files produced for each SDK: 737 The following list shows the files produced for each SDK:
765 <itemizedlist> 738 <itemizedlist>
766 <listitem><para><filename>files-in-sdk.txt:</filename> 739 <listitem><para><filename>files-in-sdk.txt:</filename>
@@ -830,7 +803,8 @@
830 803
831 <para> 804 <para>
832 To see any changes that have occurred (assuming you have 805 To see any changes that have occurred (assuming you have
833 <filename>BUILDHISTORY_COMMIT = "1"</filename>), you can simply 806 <link linkend='var-BUILDHISTORY_COMMIT'><filename>BUILDHISTORY_COMMIT = "1"</filename></link>),
807 you can simply
834 use any Git command that allows you to view the history of 808 use any Git command that allows you to view the history of
835 a repository. 809 a repository.
836 Here is one method: 810 Here is one method: