diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-01-08 14:17:56 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-01-21 21:57:58 +0000 |
| commit | 6d65a98fa99559c4f327303cd34229e42bc17b44 (patch) | |
| tree | 9423728d95d53cbe7aa870a4aacb7e18af637279 /documentation | |
| parent | a1cb6dbc366f48adb5e05fcf8fee26f5e6cc9525 (diff) | |
| download | ast2050-yocto-poky-6d65a98fa99559c4f327303cd34229e42bc17b44.zip ast2050-yocto-poky-6d65a98fa99559c4f327303cd34229e42bc17b44.tar.gz | |
dev-manual: Edits to "Unpacking Code" section.
Applied review comments to this section.
(From yocto-docs rev: f4075f61ca081df6c87abd876207da968450a8f3)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 17 |
1 files changed, 10 insertions, 7 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 36f67f1..c5ff3b2 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -1602,18 +1602,21 @@ <para> If you are fetching your source files from an upstream source - archived tarball then you normally do not need to set - <filename>S</filename>. + archived tarball and the tarball's internal structure matches + the common convention of a top-level subdirectory named + <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-BPN'><filename>BPN</filename></ulink><filename>}-${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-PV'><filename>PV</filename></ulink><filename>}</filename>, + then you do not need to set <filename>S</filename>. However, if <filename>SRC_URI</filename> specifies to fetch - source from an SCM like Git or Subversion, your recipe needs - to define <filename>S</filename>. + source from an archive that does not use this convention, + or from an SCM like Git or Subversion, your recipe needs to + define <filename>S</filename>. </para> <para> If processing your recipe using BitBake successfully unpacks - the source files, you need to be sure that the structure - created in <filename>${S}</filename> matches the structure - from the source. + the source files, you need to be sure that the directory + pointed to by <filename>${S}</filename> matches the structure + of the source. </para> </section> |
