summaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual/technical-details.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/poky-ref-manual/technical-details.xml')
-rw-r--r--documentation/poky-ref-manual/technical-details.xml15
1 files changed, 11 insertions, 4 deletions
diff --git a/documentation/poky-ref-manual/technical-details.xml b/documentation/poky-ref-manual/technical-details.xml
index 2e30df1604..654d9252a9 100644
--- a/documentation/poky-ref-manual/technical-details.xml
+++ b/documentation/poky-ref-manual/technical-details.xml
@@ -129,7 +129,7 @@
129 between metadata files. 129 between metadata files.
130 An example is the Autotools class, which contains 130 An example is the Autotools class, which contains
131 common settings for any application that Autotools uses. 131 common settings for any application that Autotools uses.
132 The "<link linkend='ref-classes'>Reference: Classes</link>" chapter provides details 132 The "<link linkend='ref-classes'>Classes</link>" chapter provides details
133 about common classes and how to use them. 133 about common classes and how to use them.
134 </para> 134 </para>
135 </section> 135 </section>
@@ -143,7 +143,7 @@
143 These files fall into several areas that define machine configuration options, 143 These files fall into several areas that define machine configuration options,
144 distribution configuration options, compiler tuning options, general common configuration 144 distribution configuration options, compiler tuning options, general common configuration
145 options and user configuration options (<filename>local.conf</filename>, which is found 145 options and user configuration options (<filename>local.conf</filename>, which is found
146 in the <ulink url='build-directory'>build directory</ulink>). 146 in the <ulink url='build-directory'>Build Directory</ulink>).
147 </para> 147 </para>
148 </section> 148 </section>
149</section> 149</section>
@@ -304,7 +304,7 @@
304 Information based on direct inputs is referred to as the "basehash" in the 304 Information based on direct inputs is referred to as the "basehash" in the
305 code. 305 code.
306 However, there is still the question of a task's indirect inputs - the 306 However, there is still the question of a task's indirect inputs - the
307 things that were already built and present in the build directory. 307 things that were already built and present in the Build Directory.
308 The checksum (or signature) for a particular task needs to add the hashes 308 The checksum (or signature) for a particular task needs to add the hashes
309 of all the tasks on which the particular task depends. 309 of all the tasks on which the particular task depends.
310 Choosing which dependencies to add is a policy decision. 310 Choosing which dependencies to add is a policy decision.
@@ -650,7 +650,7 @@
650 Yocto Project, you can follow these steps to use the x32 spABI: 650 Yocto Project, you can follow these steps to use the x32 spABI:
651 <itemizedlist> 651 <itemizedlist>
652 <listitem><para>Add the <filename>experimental/meta-x32</filename> layer to your local 652 <listitem><para>Add the <filename>experimental/meta-x32</filename> layer to your local
653 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink>. 653 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
654 You can find the <filename>experimental/meta-x32</filename> source repository at 654 You can find the <filename>experimental/meta-x32</filename> source repository at
655 <ulink url='&YOCTO_GIT_URL;'></ulink>.</para></listitem> 655 <ulink url='&YOCTO_GIT_URL;'></ulink>.</para></listitem>
656 <listitem><para>Edit your <filename>conf/bblayers.conf</filename> file so that it includes 656 <listitem><para>Edit your <filename>conf/bblayers.conf</filename> file so that it includes
@@ -698,6 +698,13 @@
698 which by default are disabled. 698 which by default are disabled.
699 </para> 699 </para>
700 700
701 <para>
702 For information that can help you maintain compliance with various open
703 source licensing during the lifecycle of the product, see the
704 "<ulink url='&YOCTO_DOCS_DEV_URL;#maintaining-open-source-license-compliance-during-your-products-lifecycle'>Maintaining Open Source License Compliance During Your Project's Lifecycle</ulink>" section
705 in the Yocto Project Development Manual.
706 </para>
707
701 <section id="usingpoky-configuring-LIC_FILES_CHKSUM"> 708 <section id="usingpoky-configuring-LIC_FILES_CHKSUM">
702 <title>Tracking License Changes</title> 709 <title>Tracking License Changes</title>
703 710