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)
downloadast2050-yocto-poky-b27a930866f19622933cf1c3e78b9311879acec4.zip
ast2050-yocto-poky-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 18cf8f6..37d4a3f 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1331,10 +1331,10 @@
After the build, you can examine these to determine how well
the build went.
<note>
- You can find individual log files for individual recipes in
- their <filename>temp</filename> directory (e.g.
+ You can find log files for each task in the recipe's
+ <filename>temp</filename> directory (e.g.
<filename>poky/build/tmp/work/qemux86-poky-linux/foo/1.3.0-r0/temp</filename>).
- Log files are named <filename>log.do_&lt;taskname&gt;</filename>
+ Log files are named <filename>log.do&lt;taskname&gt;</filename>
(e.g. <filename>log.do_configure</filename>,
<filename>log.do_fetch</filename>, and
<filename>log.do_compile</filename>).
@@ -1716,13 +1716,24 @@
<title>Configuring the Recipe</title>
<para>
- Configuration, such as build-time or runtime dependencies,
- is typically accomplished by running a configure script with
- some options, or by modifying a build configuration file.
Most software provides some means of setting build-time
configuration options before compilation.
- You can often find build-time or runtime dependencies in the
- software's documentation.
+ Typically, setting these options is accomplished by running a
+ configure script with some options, or by modifying a build
+ configuration file.
+ </para>
+
+ <para>
+ A major part of build-time configuration is about checking for
+ build-time dependencies and possibly enabling optional
+ functionality as a result.
+ You need to specify any build-time dependencies for the
+ software you are building in your recipe's
+ <ulink url='&YOCTO_DOCS_REF_URL;#var-DEPENDS'><filename>DEPENDS</filename></ulink>
+ value, in terms of other recipes that satisfy those
+ dependencies.
+ You can often find build-time or runtime
+ dependencies described in the software's documentation.
</para>
<para>
OpenPOWER on IntegriCloud