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>
This commit is contained in:
Scott Rifenbark
2014-01-08 14:17:56 -06:00
committed by Richard Purdie
parent a1cb6dbc36
commit 6d65a98fa9

View File

@@ -1602,18 +1602,21 @@
<para> <para>
If you are fetching your source files from an upstream source If you are fetching your source files from an upstream source
archived tarball then you normally do not need to set archived tarball and the tarball's internal structure matches
<filename>S</filename>. 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 However, if <filename>SRC_URI</filename> specifies to fetch
source from an SCM like Git or Subversion, your recipe needs source from an archive that does not use this convention,
to define <filename>S</filename>. or from an SCM like Git or Subversion, your recipe needs to
define <filename>S</filename>.
</para> </para>
<para> <para>
If processing your recipe using BitBake successfully unpacks If processing your recipe using BitBake successfully unpacks
the source files, you need to be sure that the structure the source files, you need to be sure that the directory
created in <filename>${S}</filename> matches the structure pointed to by <filename>${S}</filename> matches the structure
from the source. of the source.
</para> </para>
</section> </section>