diff options
| author |   Scott Rifenbark <scott.m.rifenbark@intel.com> | 2015-05-18 13:56:39 -0600 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-07-28 18:02:30 +0100 |
| commit | 7b1697bd1583a28d49c1364de079a0f441671d41 (patch) | |
| tree | 2dbac64114b81009023e7925e30dd7c0d952eb6a /documentation/kernel-dev | |
| parent | 7baadd86ee1386756e3bc3ef7fd02d5d1367068f (diff) | |
| download | openembedded-core-contrib-7b1697bd1583a28d49c1364de079a0f441671d41.tar.gz | |
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 <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-dev')
| -rw-r--r-- | documentation/kernel-dev/kernel-dev-common.xml | 9 |
1 files changed, 8 insertions, 1 deletions
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: <literallayout class='monospaced'> $ bitbake linux-yocto -c kernel_configme -f - </literallayout></para></listitem> + </literallayout> + This step ensures that you will be creating a + <filename>.config</filename> 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 + <filename>menuconfig</filename>. + </para></listitem> <listitem><para>Run the <filename>menuconfig</filename> command: <literallayout class='monospaced'> |