From 2c0358ccc7db0f232f70a0910368f391b9004782 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 18 Dec 2012 16:02:16 -0600 Subject: kernel-dev: Re-write of "Iterative Development" section. (From yocto-docs rev: fe86005486a9bf41307546bcfa7d718e0e95abf9) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/kernel-dev/kernel-dev-common.xml | 21 ++++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) (limited to 'documentation/kernel-dev') 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. Iterative Development - 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. + + + + As you read this section, be sure to substitute "linux-yocto" with + the name of the Linux kernel recipe with which you are working. + + + + Original Text: + +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. +
-- cgit v1.2.3-54-g00ecf