summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml35
1 files changed, 20 insertions, 15 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index bab68a1bb9..fb991fa4cb 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -4771,23 +4771,27 @@
4771 $ echo "CONFIG_SMP=y" >> my_smp.cfg 4771 $ echo "CONFIG_SMP=y" >> my_smp.cfg
4772 </literallayout> 4772 </literallayout>
4773 <note> 4773 <note>
4774 All configuration files must use the <filename>.cfg</filename> extension in order 4774 All configuration fragment files must use the
4775 for the OpenEmbedded build system to recognize them as a configuration fragment. 4775 <filename>.cfg</filename> extension in order for the
4776 OpenEmbedded build system to recognize them as a
4777 configuration fragment.
4776 </note> 4778 </note>
4777 </para> 4779 </para>
4778 4780
4779 <para> 4781 <para>
4780 Where do you put your configuration files? 4782 Where do you put your configuration fragment files?
4781 You can place these configuration files in the same area pointed to by 4783 You can place these files in the same area pointed to by
4782 <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>. 4784 <ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>.
4783 The OpenEmbedded build system will pick up the configuration and add it to the 4785 The OpenEmbedded build system picks up the configuration and
4784 kernel's configuration. 4786 adds it to the kernel's configuration.
4785 For example, suppose you had a set of configuration options in a file called 4787 For example, suppose you had a set of configuration options
4786 <filename>myconfig.cfg</filename>. 4788 in a file called <filename>myconfig.cfg</filename>.
4787 If you put that file inside a directory named <filename>linux-yocto</filename> 4789 If you put that file inside a directory named
4788 that resides in the same directory as the kernel's append file and then add 4790 <filename>linux-yocto</filename> that resides in the same
4789 a <filename>SRC_URI</filename> statement such as the following to the kernel's append file, 4791 directory as the kernel's append file and then add a
4790 those configuration options will be picked up and applied when the kernel is built. 4792 <filename>SRC_URI</filename> statement such as the following
4793 to the kernel's append file, those configuration options
4794 will be picked up and applied when the kernel is built.
4791 <literallayout class='monospaced'> 4795 <literallayout class='monospaced'>
4792 SRC_URI += "file://myconfig.cfg" 4796 SRC_URI += "file://myconfig.cfg"
4793 </literallayout> 4797 </literallayout>
@@ -4843,9 +4847,10 @@
4843 4847
4844 <para> 4848 <para>
4845 For each output warning, a message points to the file 4849 For each output warning, a message points to the file
4846 that contains a list of the options and a pointer to the config 4850 that contains a list of the options and a pointer to the
4847 fragment that defines them. 4851 configuration fragment that defines them.
4848 Collectively, the files are the key to streamlining the configuration. 4852 Collectively, the files are the key to streamlining the
4853 configuration.
4849 </para> 4854 </para>
4850 4855
4851 <para> 4856 <para>