dev-manual: Minor edits to "Configuring the Kernel" section.
(From yocto-docs rev: 26df09f863a0e56748a34efe4a9b2d1b02ccaa99) 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
72169b2928
commit
8c43d0fa52
|
@ -4771,23 +4771,27 @@
|
|||
$ echo "CONFIG_SMP=y" >> my_smp.cfg
|
||||
</literallayout>
|
||||
<note>
|
||||
All configuration files must use the <filename>.cfg</filename> extension in order
|
||||
for the OpenEmbedded build system to recognize them as a configuration fragment.
|
||||
All configuration fragment files must use the
|
||||
<filename>.cfg</filename> extension in order for the
|
||||
OpenEmbedded build system to recognize them as a
|
||||
configuration fragment.
|
||||
</note>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Where do you put your configuration files?
|
||||
You can place these configuration files in the same area pointed to by
|
||||
Where do you put your configuration fragment files?
|
||||
You can place these files in the same area pointed to by
|
||||
<ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>.
|
||||
The OpenEmbedded build system will pick up the configuration and add it to the
|
||||
kernel's configuration.
|
||||
For example, suppose you had a set of configuration options in a file called
|
||||
<filename>myconfig.cfg</filename>.
|
||||
If you put that file inside a directory named <filename>linux-yocto</filename>
|
||||
that resides in the same directory as the kernel's append file and then add
|
||||
a <filename>SRC_URI</filename> statement such as the following to the kernel's append file,
|
||||
those configuration options will be picked up and applied when the kernel is built.
|
||||
The OpenEmbedded build system picks up the configuration and
|
||||
adds it to the kernel's configuration.
|
||||
For example, suppose you had a set of configuration options
|
||||
in a file called <filename>myconfig.cfg</filename>.
|
||||
If you put that file inside a directory named
|
||||
<filename>linux-yocto</filename> that resides in the same
|
||||
directory as the kernel's append file and then add a
|
||||
<filename>SRC_URI</filename> statement such as the following
|
||||
to the kernel's append file, those configuration options
|
||||
will be picked up and applied when the kernel is built.
|
||||
<literallayout class='monospaced'>
|
||||
SRC_URI += "file://myconfig.cfg"
|
||||
</literallayout>
|
||||
|
@ -4843,9 +4847,10 @@
|
|||
|
||||
<para>
|
||||
For each output warning, a message points to the file
|
||||
that contains a list of the options and a pointer to the config
|
||||
fragment that defines them.
|
||||
Collectively, the files are the key to streamlining the configuration.
|
||||
that contains a list of the options and a pointer to the
|
||||
configuration fragment that defines them.
|
||||
Collectively, the files are the key to streamlining the
|
||||
configuration.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
|
Loading…
Reference in New Issue