summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-12-18 16:02:16 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-01-16 15:59:06 +0000
commit2c0358ccc7db0f232f70a0910368f391b9004782 (patch)
tree287e6f0c6574434838370baf5fb5c8ac131644db /documentation
parent716306ad2bf313ff490dd131650c718218134be0 (diff)
downloadpoky-2c0358ccc7db0f232f70a0910368f391b9004782.tar.gz
kernel-dev: Re-write of "Iterative Development" section.
(From yocto-docs rev: fe86005486a9bf41307546bcfa7d718e0e95abf9) 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/kernel-dev/kernel-dev-common.xml21
1 files changed, 20 insertions, 1 deletions
diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml
index fbe43213e2..6c55a572b0 100644
--- a/documentation/kernel-dev/kernel-dev-common.xml
+++ b/documentation/kernel-dev/kernel-dev-common.xml
@@ -258,13 +258,32 @@ apply the new configuration before rebuilding the Linux kernel.
258 <title>Iterative Development</title> 258 <title>Iterative Development</title>
259 259
260 <para> 260 <para>
261 If you do not have existing patches or configuration files, you can easily 261 If you do not have existing patches or configuration files,
262 you can iteratively generate them from within the BitBake build
263 environment as described within this section.
264 During an iterative workflow, running a previously completed BitBake
265 task causes BitBake to invalidate the tasks that follow that
266 task in the build sequence.
267 This invalidation causes the tasks to rebuild the next
268 time you invoke the build.
269 </para>
270
271 <para>
272 As you read this section, be sure to substitute "linux-yocto" with
273 the name of the Linux kernel recipe with which you are working.
274 </para>
275
276 <para>
277 Original Text:
278 <literallayout class='monospaced'>
279If you do not have existing patches or configuration files, you can easily
262generate them from within the bitbake build environment, as will be described 280generate them from within the bitbake build environment, as will be described
263below. As you do, running previously completed bitbake tasks will cause bitbake 281below. As you do, running previously completed bitbake tasks will cause bitbake
264to invalidate the tasks that follow them in the build sequence, causing them to 282to invalidate the tasks that follow them in the build sequence, causing them to
265rebuild at the next invocation of the build. Throughout this section, be sure to 283rebuild at the next invocation of the build. Throughout this section, be sure to
266substitute "linux-yocto" with the name of the Linux kernel recipe you are 284substitute "linux-yocto" with the name of the Linux kernel recipe you are
267working with. 285working with.
286 </literallayout>
268 </para> 287 </para>
269 288
270 <section id='generating-configuration-files'> 289 <section id='generating-configuration-files'>