diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-12-18 16:02:16 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-01-16 15:59:06 +0000 |
commit | 2c0358ccc7db0f232f70a0910368f391b9004782 (patch) | |
tree | 287e6f0c6574434838370baf5fb5c8ac131644db /documentation/kernel-dev/kernel-dev-common.xml | |
parent | 716306ad2bf313ff490dd131650c718218134be0 (diff) | |
download | poky-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/kernel-dev/kernel-dev-common.xml')
-rw-r--r-- | documentation/kernel-dev/kernel-dev-common.xml | 21 |
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'> | ||
279 | If you do not have existing patches or configuration files, you can easily | ||
262 | generate them from within the bitbake build environment, as will be described | 280 | generate them from within the bitbake build environment, as will be described |
263 | below. As you do, running previously completed bitbake tasks will cause bitbake | 281 | below. As you do, running previously completed bitbake tasks will cause bitbake |
264 | to invalidate the tasks that follow them in the build sequence, causing them to | 282 | to invalidate the tasks that follow them in the build sequence, causing them to |
265 | rebuild at the next invocation of the build. Throughout this section, be sure to | 283 | rebuild at the next invocation of the build. Throughout this section, be sure to |
266 | substitute "linux-yocto" with the name of the Linux kernel recipe you are | 284 | substitute "linux-yocto" with the name of the Linux kernel recipe you are |
267 | working with. | 285 | working with. |
286 | </literallayout> | ||
268 | </para> | 287 | </para> |
269 | 288 | ||
270 | <section id='generating-configuration-files'> | 289 | <section id='generating-configuration-files'> |