summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual/dev-manual-common-tasks.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml17
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 36f67f10c3..c5ff3b29b5 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1602,18 +1602,21 @@
1602 1602
1603 <para> 1603 <para>
1604 If you are fetching your source files from an upstream source 1604 If you are fetching your source files from an upstream source
1605 archived tarball then you normally do not need to set 1605 archived tarball and the tarball's internal structure matches
1606 <filename>S</filename>. 1606 the common convention of a top-level subdirectory named
1607 <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>,
1608 then you do not need to set <filename>S</filename>.
1607 However, if <filename>SRC_URI</filename> specifies to fetch 1609 However, if <filename>SRC_URI</filename> specifies to fetch
1608 source from an SCM like Git or Subversion, your recipe needs 1610 source from an archive that does not use this convention,
1609 to define <filename>S</filename>. 1611 or from an SCM like Git or Subversion, your recipe needs to
1612 define <filename>S</filename>.
1610 </para> 1613 </para>
1611 1614
1612 <para> 1615 <para>
1613 If processing your recipe using BitBake successfully unpacks 1616 If processing your recipe using BitBake successfully unpacks
1614 the source files, you need to be sure that the structure 1617 the source files, you need to be sure that the directory
1615 created in <filename>${S}</filename> matches the structure 1618 pointed to by <filename>${S}</filename> matches the structure
1616 from the source. 1619 of the source.
1617 </para> 1620 </para>
1618 </section> 1621 </section>
1619 1622