summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-01-13 09:27:03 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-01-21 21:58:02 +0000
commitb27a930866f19622933cf1c3e78b9311879acec4 (patch)
tree85843a1e18e9a9b12db201a2cdf59dfcc45b0957 /documentation
parent5837061a68e02eff6042990cd18ddf6cdddeb56c (diff)
downloadpoky-b27a930866f19622933cf1c3e78b9311879acec4.tar.gz
dev-manual: Added review comments to "Writing a New Recipe" section.
These changes are Paul Eggleton's fourth review change. (From yocto-docs rev: 8470c1b516f7799148b4e2eae28534730e93b58b) 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.xml27
1 files changed, 19 insertions, 8 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 18cf8f67a6..37d4a3f3d4 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1331,10 +1331,10 @@
1331 After the build, you can examine these to determine how well 1331 After the build, you can examine these to determine how well
1332 the build went. 1332 the build went.
1333 <note> 1333 <note>
1334 You can find individual log files for individual recipes in 1334 You can find log files for each task in the recipe's
1335 their <filename>temp</filename> directory (e.g. 1335 <filename>temp</filename> directory (e.g.
1336 <filename>poky/build/tmp/work/qemux86-poky-linux/foo/1.3.0-r0/temp</filename>). 1336 <filename>poky/build/tmp/work/qemux86-poky-linux/foo/1.3.0-r0/temp</filename>).
1337 Log files are named <filename>log.do_&lt;taskname&gt;</filename> 1337 Log files are named <filename>log.do&lt;taskname&gt;</filename>
1338 (e.g. <filename>log.do_configure</filename>, 1338 (e.g. <filename>log.do_configure</filename>,
1339 <filename>log.do_fetch</filename>, and 1339 <filename>log.do_fetch</filename>, and
1340 <filename>log.do_compile</filename>). 1340 <filename>log.do_compile</filename>).
@@ -1716,13 +1716,24 @@
1716 <title>Configuring the Recipe</title> 1716 <title>Configuring the Recipe</title>
1717 1717
1718 <para> 1718 <para>
1719 Configuration, such as build-time or runtime dependencies,
1720 is typically accomplished by running a configure script with
1721 some options, or by modifying a build configuration file.
1722 Most software provides some means of setting build-time 1719 Most software provides some means of setting build-time
1723 configuration options before compilation. 1720 configuration options before compilation.
1724 You can often find build-time or runtime dependencies in the 1721 Typically, setting these options is accomplished by running a
1725 software's documentation. 1722 configure script with some options, or by modifying a build
1723 configuration file.
1724 </para>
1725
1726 <para>
1727 A major part of build-time configuration is about checking for
1728 build-time dependencies and possibly enabling optional
1729 functionality as a result.
1730 You need to specify any build-time dependencies for the
1731 software you are building in your recipe's
1732 <ulink url='&YOCTO_DOCS_REF_URL;#var-DEPENDS'><filename>DEPENDS</filename></ulink>
1733 value, in terms of other recipes that satisfy those
1734 dependencies.
1735 You can often find build-time or runtime
1736 dependencies described in the software's documentation.
1726 </para> 1737 </para>
1727 1738
1728 <para> 1739 <para>