diff options
Diffstat (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml')
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index ec9b2183e9..f631f98e18 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml | |||
| @@ -771,7 +771,7 @@ so that there are some definite steps on how to do this. I need more detail her | |||
| 771 | 771 | ||
| 772 | <para> | 772 | <para> |
| 773 | During a build, the unpacked temporary source code used by recipes | 773 | During a build, the unpacked temporary source code used by recipes |
| 774 | to build packages is available in the Yocto Project build directory as | 774 | to build packages is available in the Yocto Project Build Directory as |
| 775 | defined by the | 775 | defined by the |
| 776 | <filename><ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#var-S'>S</ulink></filename> variable. | 776 | <filename><ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#var-S'>S</ulink></filename> variable. |
| 777 | Below is the default value for the <filename>S</filename> variable as defined in the | 777 | Below is the default value for the <filename>S</filename> variable as defined in the |
| @@ -802,7 +802,7 @@ so that there are some definite steps on how to do this. I need more detail her | |||
| 802 | </literallayout> | 802 | </literallayout> |
| 803 | Let's look at an example without variables. | 803 | Let's look at an example without variables. |
| 804 | Assuming a Yocto Project Files top-level directory named <filename>poky</filename> | 804 | Assuming a Yocto Project Files top-level directory named <filename>poky</filename> |
| 805 | and a default Yocto Project build directory of <filename>poky/build</filename>, | 805 | and a default Yocto Project Build Directory of <filename>poky/build</filename>, |
| 806 | the following is the work directory for the <filename>acl</filename> package: | 806 | the following is the work directory for the <filename>acl</filename> package: |
| 807 | <literallayout class='monospaced'> | 807 | <literallayout class='monospaced'> |
| 808 | ~/poky/build/tmp/work/i586-poky-linux/acl-2.2.51-r3 | 808 | ~/poky/build/tmp/work/i586-poky-linux/acl-2.2.51-r3 |
| @@ -815,7 +815,7 @@ so that there are some definite steps on how to do this. I need more detail her | |||
| 815 | ${TMPDIR}/work/${MACHINE}-poky-${TARGET_OS}/${PN}-${PV}-${PR} | 815 | ${TMPDIR}/work/${MACHINE}-poky-${TARGET_OS}/${PN}-${PV}-${PR} |
| 816 | </literallayout> | 816 | </literallayout> |
| 817 | Again, assuming a Yocto Project Files top-level directory named <filename>poky</filename> | 817 | Again, assuming a Yocto Project Files top-level directory named <filename>poky</filename> |
| 818 | and a default Yocto Project build directory of <filename>poky/build</filename>, the | 818 | and a default Yocto Project Build Directory of <filename>poky/build</filename>, the |
| 819 | following is the work directory for the <filename>acl</filename> package that is being | 819 | following is the work directory for the <filename>acl</filename> package that is being |
| 820 | built for a MIPS-based device: | 820 | built for a MIPS-based device: |
| 821 | <literallayout class='monospaced'> | 821 | <literallayout class='monospaced'> |
| @@ -861,7 +861,7 @@ so that there are some definite steps on how to do this. I need more detail her | |||
| 861 | <orderedlist> | 861 | <orderedlist> |
| 862 | <listitem><para><emphasis>Find the Source Code:</emphasis> | 862 | <listitem><para><emphasis>Find the Source Code:</emphasis> |
| 863 | The temporary source code used by the Yocto Project build system is kept in the | 863 | The temporary source code used by the Yocto Project build system is kept in the |
| 864 | Yocto Project build directory. | 864 | Yocto Project Build Directory. |
| 865 | See the | 865 | See the |
| 866 | "<link linkend='finding-the-temporary-source-code'>Finding the Temporary Source Code</link>" | 866 | "<link linkend='finding-the-temporary-source-code'>Finding the Temporary Source Code</link>" |
| 867 | section to learn how to locate the directory that has the temporary source code for a | 867 | section to learn how to locate the directory that has the temporary source code for a |
| @@ -957,7 +957,7 @@ so that there are some definite steps on how to do this. I need more detail her | |||
| 957 | <orderedlist> | 957 | <orderedlist> |
| 958 | <listitem><para><emphasis>Find the Source Code:</emphasis> | 958 | <listitem><para><emphasis>Find the Source Code:</emphasis> |
| 959 | The temporary source code used by the Yocto Project build system is kept in the | 959 | The temporary source code used by the Yocto Project build system is kept in the |
| 960 | Yocto Project build directory. | 960 | Yocto Project Build Directory. |
| 961 | See the | 961 | See the |
| 962 | "<link linkend='finding-the-temporary-source-code'>Finding the Temporary Source Code</link>" | 962 | "<link linkend='finding-the-temporary-source-code'>Finding the Temporary Source Code</link>" |
| 963 | section to learn how to locate the directory that has the temporary source code for a | 963 | section to learn how to locate the directory that has the temporary source code for a |
| @@ -1141,7 +1141,8 @@ so that there are some definite steps on how to do this. I need more detail her | |||
| 1141 | After you have set up the recipes, you need to define the actual | 1141 | After you have set up the recipes, you need to define the actual |
| 1142 | combination of multiple libraries you want to build. | 1142 | combination of multiple libraries you want to build. |
| 1143 | You accomplish this through your <filename>local.conf</filename> | 1143 | You accomplish this through your <filename>local.conf</filename> |
| 1144 | configuration file in the Yocto Project build directory. | 1144 | configuration file in the |
| 1145 | <link linkend='yocto-project-build-directory'>Yocto Project Build Directory</link>. | ||
| 1145 | An example configuration would be as follows: | 1146 | An example configuration would be as follows: |
| 1146 | <literallayout class='monospaced'> | 1147 | <literallayout class='monospaced'> |
| 1147 | MACHINE = "qemux86-64" | 1148 | MACHINE = "qemux86-64" |
| @@ -1185,8 +1186,8 @@ so that there are some definite steps on how to do this. I need more detail her | |||
| 1185 | <itemizedlist> | 1186 | <itemizedlist> |
| 1186 | <listitem><para>A unique architecture is defined for the Multilib packages, | 1187 | <listitem><para>A unique architecture is defined for the Multilib packages, |
| 1187 | along with creating a unique deploy folder under | 1188 | along with creating a unique deploy folder under |
| 1188 | <filename>tmp/deploy/rpm</filename> in the Yocto | 1189 | <filename>tmp/deploy/rpm</filename> in the |
| 1189 | Project build directory. | 1190 | <link linkend='yocto-project-build-directory'>Yocto Project Build Directory</link>. |
| 1190 | For example, consider <filename>lib32</filename> in a | 1191 | For example, consider <filename>lib32</filename> in a |
| 1191 | <filename>qemux86-64</filename> image. | 1192 | <filename>qemux86-64</filename> image. |
| 1192 | The possible architectures in the system are "all", "qemux86_64", | 1193 | The possible architectures in the system are "all", "qemux86_64", |
