diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-02-14 13:17:15 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-03-08 12:07:56 -0800 |
| commit | 7a88a29c6750d80d6277e243e9504cb3958ceed2 (patch) | |
| tree | a4005619a3964039b4fcfd795d4da16661f2db3a | |
| parent | ea70ac509bd898171d85ca6f3b2e7b033e528a68 (diff) | |
| download | poky-7a88a29c6750d80d6277e243e9504cb3958ceed2.tar.gz | |
documentation/dev-manual/dev-manual-common-tasks.xml: review comments applied
Applied the review comments from both Paul Eggleton and Joshua
Lock for the "Modifying Package Source Code" section.
Reported-by: Paul Eggleton <paul.eggleton@intel.com>
Reported-by: Joshua Lock <joshual.lock@intel.com>
(From yocto-docs rev: 276c13517c7edda8407fdf82c36d14029c5fcee4)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index db6c29fdc3..1199669ab0 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml | |||
| @@ -775,11 +775,11 @@ so that there are some definite steps on how to do this. I need more detail her | |||
| 775 | ${TMPDIR}/work/${PACKAGE_ARCH}-poky-${TARGET_OS}/${PN}-${PV}-${PR} | 775 | ${TMPDIR}/work/${PACKAGE_ARCH}-poky-${TARGET_OS}/${PN}-${PV}-${PR} |
| 776 | </literallayout> | 776 | </literallayout> |
| 777 | Assuming a Yocto Project Files top-level directory named <filename>poky</filename> | 777 | Assuming a Yocto Project Files top-level directory named <filename>poky</filename> |
| 778 | and a default Yocto Project build directory of <filename>poky/build</filename>, here | 778 | and a default Yocto Project build directory of <filename>poky/build</filename>, |
| 779 | is an example temporary package source code location for the | 779 | the following is the temporary package source code location for the |
| 780 | <filename>v86d</filename> package: | 780 | <filename>acl</filename> package: |
| 781 | <literallayout class='monospaced'> | 781 | <literallayout class='monospaced'> |
| 782 | ~/poky/build/tmp/work/qemux86-poky-linux/v86d-01.9-r0 | 782 | ~/poky/build/tmp/work/i586-poky-linux/acl-2.2.51-r3 |
| 783 | </literallayout> | 783 | </literallayout> |
| 784 | </para> | 784 | </para> |
| 785 | 785 | ||
| @@ -789,20 +789,14 @@ so that there are some definite steps on how to do this. I need more detail her | |||
| 789 | ${TMPDIR}/work/${MACHINE}-poky-${TARGET_OS}/${PN}-${PV}-${PR} | 789 | ${TMPDIR}/work/${MACHINE}-poky-${TARGET_OS}/${PN}-${PV}-${PR} |
| 790 | </literallayout> | 790 | </literallayout> |
| 791 | Again, assuming a Yocto Project Files top-level directory named <filename>poky</filename> | 791 | Again, assuming a Yocto Project Files top-level directory named <filename>poky</filename> |
| 792 | and a default Yocto Project build directory of <filename>poky/build</filename>, here | 792 | and a default Yocto Project build directory of <filename>poky/build</filename>, the |
| 793 | is an example temporary package source code location for the | 793 | following is the temporary package source code location for the |
| 794 | <filename>acl</filename> package that is dependent upon a MIPS-based device: | 794 | <filename>acl</filename> package that is being built for a MIPS-based device: |
| 795 | <literallayout class='monospaced'> | 795 | <literallayout class='monospaced'> |
| 796 | ~/poky/build/tmp/work/mips-poky-linux/acl-2.2.51-r2 | 796 | ~/poky/build/tmp/work/mips-poky-linux/acl-2.2.51-r2 |
| 797 | </literallayout> | 797 | </literallayout> |
| 798 | </para> | 798 | </para> |
| 799 | 799 | ||
| 800 | <tip> | ||
| 801 | Be sure the package recipe sets the | ||
| 802 | <filename><ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#var-S'>S</ulink></filename> variable to something | ||
| 803 | other than the standard <filename>WORKDIR/PN-PV/</filename> value. | ||
| 804 | </tip> | ||
| 805 | |||
| 806 | <para> | 800 | <para> |
| 807 | Once you have modified the package source code, the easiest way to test your changes | 801 | Once you have modified the package source code, the easiest way to test your changes |
| 808 | is by calling the <filename>compile</filename> task as shown in the following example: | 802 | is by calling the <filename>compile</filename> task as shown in the following example: |
| @@ -816,7 +810,13 @@ so that there are some definite steps on how to do this. I need more detail her | |||
| 816 | option forces re-execution of the specified task. | 810 | option forces re-execution of the specified task. |
| 817 | You can call other tasks this way as well. | 811 | You can call other tasks this way as well. |
| 818 | <note>All the modifications you make to the temporary package source code | 812 | <note>All the modifications you make to the temporary package source code |
| 819 | disappear once you <filename>-c clean</filename> for the package.</note> | 813 | disappear once you <filename>-c clean</filename> or |
| 814 | <filename>-c cleanall</filename> with BitBake for the package. | ||
| 815 | Modifications will also disappear if you use the <filename>rm_work</filename> | ||
| 816 | feature as described in the | ||
| 817 | "<ulink url='http://www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html#building-image'>Building an Image</ulink>" section | ||
| 818 | of the Yocto Project Quick Start. | ||
| 819 | </note> | ||
| 820 | </para> | 820 | </para> |
| 821 | </section> | 821 | </section> |
| 822 | 822 | ||
