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>
This commit is contained in:
Scott Rifenbark
2012-12-18 16:02:16 -06:00
committed by Richard Purdie
parent 716306ad2b
commit 2c0358ccc7

View File

@@ -258,13 +258,32 @@ apply the new configuration before rebuilding the Linux kernel.
<title>Iterative Development</title>
<para>
If you do not have existing patches or configuration files, you can easily
If you do not have existing patches or configuration files,
you can iteratively generate them from within the BitBake build
environment as described within this section.
During an iterative workflow, running a previously completed BitBake
task causes BitBake to invalidate the tasks that follow that
task in the build sequence.
This invalidation causes the tasks to rebuild the next
time you invoke the build.
</para>
<para>
As you read this section, be sure to substitute "linux-yocto" with
the name of the Linux kernel recipe with which you are working.
</para>
<para>
Original Text:
<literallayout class='monospaced'>
If you do not have existing patches or configuration files, you can easily
generate them from within the bitbake build environment, as will be described
below. As you do, running previously completed bitbake tasks will cause bitbake
to invalidate the tasks that follow them in the build sequence, causing them to
rebuild at the next invocation of the build. Throughout this section, be sure to
substitute "linux-yocto" with the name of the Linux kernel recipe you are
working with.
</literallayout>
</para>
<section id='generating-configuration-files'>