From 7b1697bd1583a28d49c1364de079a0f441671d41 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 18 May 2015 13:56:39 -0600 Subject: kernel-dev: Added detail to start of generating config file Fixes [YOCTO #7474] The "Generating Configuration Files" section has a procedure that starts with a step to complete a build at least through the kernel configuration task. This is needed but we could use a bit of explanation here. I added some rationale behind why you should do this. (From yocto-docs rev: 63df3474f4ed211dd6b7d1cf4f4e90bbc92c2595) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/kernel-dev/kernel-dev-common.xml | 9 ++++++++- 1 file changed, 8 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 25a41d381d..c0acac8316 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml @@ -347,7 +347,14 @@ configuration task as follows: $ bitbake linux-yocto -c kernel_configme -f - + + This step ensures that you will be creating a + .config file from a known state. + Because situations exist where your build state might + become unknown, it is best to run the previous + command prior to starting up + menuconfig. + Run the menuconfig command: -- cgit v1.2.3-54-g00ecf