kernel-dev: Added new requirement for working with yocto-linux-custom.bb
Fixes [YOCTO #6611] Added a new step to the "Working With Your Own Sources" section so that the user is aware of needing to provide a defconfig file or configuration fragments to the SRC_URI variable when working with the yocto-linux-custom.bb recipe. (From yocto-docs rev: dd25274979f689ae9135158279080add19a98393) 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
4764062664
commit
5644756bc7
|
@ -631,15 +631,35 @@
|
|||
to store your patches and configuration files (e.g.
|
||||
<filename>linux-yocto-myproject</filename>).
|
||||
</para></listitem>
|
||||
<listitem><para>Make sure you have either a
|
||||
<filename>defconfig</filename> file or configuration
|
||||
fragment files.
|
||||
When you use the <filename>linux-yocto-custom.bb</filename>
|
||||
recipe, you must specify a configuration.
|
||||
If you do not have a <filename>defconfig</filename> file,
|
||||
you can run the following:
|
||||
<literallayout class='monospaced'>
|
||||
$ make defconfig
|
||||
</literallayout>
|
||||
After running the command, copy the resulting
|
||||
<filename>.config</filename> to the
|
||||
<filename>files</filename> directory as "defconfig" and
|
||||
then add it to the
|
||||
<ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>
|
||||
variable in the recipe.
|
||||
</para></listitem>
|
||||
<listitem><para>Edit the following variables in your recipe
|
||||
as appropriate for your project:
|
||||
<itemizedlist>
|
||||
<listitem><para><ulink url='&YOCTO_DOCS_REF_URL;#var-SRC_URI'><filename>SRC_URI</filename></ulink>:
|
||||
The <filename>SRC_URI</filename> should be a Git
|
||||
repository that uses one of the supported Git fetcher
|
||||
protocols (i.e. <filename>file</filename>,
|
||||
The <filename>SRC_URI</filename> should specify
|
||||
a Git repository that uses one of the supported Git
|
||||
fetcher protocols (i.e. <filename>file</filename>,
|
||||
<filename>git</filename>, <filename>http</filename>,
|
||||
and so forth).
|
||||
The <filename>SRC_URI</filename> variable should
|
||||
also specify either a <filename>defconfig</filename>
|
||||
file or some configuration fragment files.
|
||||
The skeleton recipe provides an example
|
||||
<filename>SRC_URI</filename> as a syntax reference.
|
||||
</para></listitem>
|
||||
|
|
Loading…
Reference in New Issue