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>
This commit is contained in:
parent
7baadd86ee
commit
7b1697bd15
|
@ -347,7 +347,14 @@
|
||||||
configuration task as follows:
|
configuration task as follows:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ bitbake linux-yocto -c kernel_configme -f
|
$ 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>
|
<listitem><para>Run the <filename>menuconfig</filename>
|
||||||
command:
|
command:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
|
|
Loading…
Reference in New Issue